Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hi folks, just to let you know i had exactly the same issue on M2 (non pro) with 10GE, probably it is a bug only affecting 10GE Nics. Issue only if you have DHCP set to auto, static IP works just fine.
 
Hi folks, just to let you know i had exactly the same issue on M2 (non pro) with 10GE, probably it is a bug only affecting 10GE Nics. Issue only if you have DHCP set to auto, static IP works just fine.
Does the 13.2.1 update fixed your issue?
 
13.2.1 did not fix the issue on my Mac mini M2 Pro. I had to set it back to manual with the setting turned off. Since I’m not running MIDI hardware or anything that would use the protocol, it doesn’t really affect me, but I’m disappointed the fix failed.
 
13.2.1 did not fix the issue on my Mac mini M2 Pro. I had to set it back to manual with the setting turned off. Since I’m not running MIDI hardware or anything that would use the protocol, it doesn’t really affect me, but I’m disappointed the fix failed.
in automatic does it say full duplex and avb mode is on ? mine has those setting and are grayed out
but is working fine now, with no packet loss
 
Hi folks, just to let you know i had exactly the same issue on M2 (non pro) with 10GE, probably it is a bug only affecting 10GE Nics. Issue only if you have DHCP set to auto, static IP works just fine.
i dont have 10ge and had the problem on the pro , is fixed now on 13.2.1 for me
let me reboot one more time and check again


edit:
is still working fine after a reboot
 
Last edited:
  • Like
Reactions: sauria
i just updated and can confirm it does fix the issue
I change back to automatic and did a test in terminal app

put this in terminal

ping -c 6 google.com

I get 0.0 packet loss

Problem solved for me
I suggest running the ping longer. I ran a ping on apple.com and it looked fixed, but after about 20 pings, it timed out on a connection. Granted it was only once, but that prompted me to run the Ookla Speedtest app again. With the bad version, Speedtest always errored out on the upload portion of the test while passing the download test. It once again errored out on the upload test with the new OS version. Try those tests to see if it’s really fixed. Seeing the Speedtest error and the single packet loss, I went back to manual configuration with AVB/EAV turned off and speed set to 2500Base-T (my network is 2500).
 
MacOS Ventura 13.2.1 seems to have fixed the issue for me as well (Mac mini M2 Pro, without 10GE upgrade). I tried a few hundred pings to multiple servers. No more packet loss with the automatic setting. Speedtest looks good as well.

edit: Ethernet has been working for about an hour now with no problems.
 
Last edited:
I suggest running the ping longer. I ran a ping on apple.com and it looked fixed, but after about 20 pings, it timed out on a connection. Granted it was only once, but that prompted me to run the Ookla Speedtest app again. With the bad version, Speedtest always errored out on the upload portion of the test while passing the download test. It once again errored out on the upload test with the new OS version. Try those tests to see if it’s really fixed. Seeing the Speedtest error and the single packet loss, I went back to manual configuration with AVB/EAV turned off and speed set to 2500Base-T (my network is 2500).
I did

ping -c 100 google.com

got 0.0 packet loss
 
I did

ping -c 100 google.com

got 0.0 packet loss
I did some further tests on my setup and it turns out the fix is partially working. While Automatic setting appears to work since I also did 100 pings and got 0% packet loss, Ookla Speedtest continued to fail 100% of the time on the upload test while having no trouble with the download test. I tried toggling settings manually and found that the key setting for me is the speed of the network. If I turn AVB/EAV back on and leave my speed at 2500Base-T, it works. Speedtest works flawlessly and the pings work. If I set network speed to auto, it fails.

The reason why it probably works for most while it fails for me is that I don’t have a normal Ethernet setup. Mine is using the 2500Mbps port of my Asus 6e router while connected on both sides by 2500Base-T network switches. Most people are probably running on Gigabit Ethernet, aka 1000Base-T, networks. It’s quite possible Apple did fix AVB/EAV but there was a second bug where auto negotiation for network speed fails above 1Gbps. I could test that, but I don’t really have enough 1Gbps switches and it would be disruptive to the rest of the family

I had to wait a couple of extra weeks to get my Mac mini because I special ordered a 10Gbps Ethernet port, so that is another difference where most people probably only got the 1Gbps Ethernet port.
 

M2 Pro Mac mini has Packet Loss over Ethernet + Solution (How to Fix)​



Can Apple release a Mac computer without any major issues? Well, if my recent experiences are an indication... it seems not.

The latest issue I ran into using the M2 Pro Mac mini is with the Ethernet. More specifically, transfer speeds seemed erratic, and it turns out it's because of packet loss.

Here's more about the issue, how to test for it yourself, and a solution on how to fix it.
 
  • Like
Reactions: sauria
Same problem here. Wifi OK, ethernet package lose, cant login to corporate website, battle.net etc…
Fixed by changing the Ethernet hardware configuration to "Manually" (the default is Automatic). You change the hardware configuration via the system settings (system settings > network > Ethernet > Details... > Hardware).
 
So as long as we set to manual then all is fine? The issue only remains if you leave it at auto?

If so I don’t mind since the network environment for a desktop is never supposed to change anyway.
 
No issues with Ethernet - did a quick test - was a little surprised how awful the 2.4GHz Wifi speed is!

I have 500Mbit cable internet (obviously, the upload pipe is throttled to ~ 100Mbit)

I'm on the Ventura beta, so I'll submit the results so, hopefully, Apple may be able to address that with a driver update - though I'll play around with the 2.4GHz channels as well.

My WAP is about 30" away from the Mini. Yes, that's inches. :D My WAP supports 802.11ax - in 2.4GHz mode, it says the Tx rate is 229Mbit.

Ethernet.png

2.4GHz Wifi.png


5GHz Wifi.png


Yep, should do some wired tests with my MBP and make sure that there's no packets loss - but no noticeable issues.
 
Last edited:
Is this fixed for everyone now? I'm still seeing packet loss when measuring even after trying all workarounds proposed here. Although the internet experience has dramatically improved since 13.2.1. According to ping even inside my home network I get 5-10% loss. But again it's almost imperceptible, probably because TCP retry masks the issue.

$ ping -c 100 192.168.0.1
--- 192.168.0.1 ping statistics ---
100 packets transmitted, 90 packets received, 10.0% packet loss
round-trip min/avg/max/stddev = 22.026/24.431/33.182/2.437 ms


WiFi works without any issues or packet loss.
 

Attachments

  • Screenshot 2023-02-21 at 10.16.27 AM.png
    Screenshot 2023-02-21 at 10.16.27 AM.png
    395.8 KB · Views: 126
Last edited:
Mac Mini Pro w/ 10GbE NIC running 13.2.1 connected to a 1GbE switch.

Have the problem of packet loss + connection becoming disconnected entirely.

No combo of auto/manual or AVB/EAV settings has fixed it permanently, i.e. it works fine for a while then happens again. Disable/Enable ethernet always fixes until the next occurrence.

Using DHCP, so have not tried w/ a manual IP set as suggested by some.

Now using a USB-1GbE adapter w/ same cable and zero problems.
 
I guess I'll also chime in, for the record: in the end, I bought a USB-2.5GbE adapter (and upgraded my switch to 2.5GbE 😅). I figured that if I'm going to have an external adapter for the mini, I might as well get something out of it! Haven't had any issues since. (Double digit uptime! 🥳)
 
  • Like
Reactions: sauria
The update to 13.3 still does not appear to have fixed it

My setup:

Mac Mini M2 Max with 1GB Ethernet

There does seem to be a latency issue as well as overall throughput (notice 68/54 for jitter) - I have FIOS and normally get 800-900mb/s

I get consistently 250-260 Mbs solid

When I connect a USB-C 1Gbps ETHERNET adapter, that works perfectly fine.

I tried going to manual mode, change duplex settings, enabled/disabled all options, and no luck

Screen shot 1 with Built-in
Screenshot 2023-03-31 at 8.58.47 AM.png


Screen shot 2: usb-c Ethernet Adapter
Screenshot 2023-03-31 at 8.59.58 AM.png
 
I'm sorry - M2 Pro

I booted the mac in Diagnostic mode and there was no issue at all - zero latency. Makes me wonder if there's a driver issue.
 
  • Like
Reactions: sauria
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.