Latest Ventura Beta 13.4 (22F5059b) has mangled network access

Hi Folks,

Just installed Latest Ventura Beta 13.4 (22F5059b) on my 2019 16 in MBP and now I have no reliable network access.

Running Ping returns:

PING 172.16.1.1 (172.16.1.1): 56 data bytes

ping: sendto: No route to host

ping: sendto: No route to host

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

64 bytes from 172.16.1.1: icmp_seq=2 ttl=255 time=3.380 ms

64 bytes from 172.16.1.1: icmp_seq=3 ttl=255 time=0.626 ms

64 bytes from 172.16.1.1: icmp_seq=4 ttl=255 time=0.656 ms

64 bytes from 172.16.1.1: icmp_seq=5 ttl=255 time=0.466 ms

64 bytes from 172.16.1.1: icmp_seq=6 ttl=255 time=0.693 ms

64 bytes from 172.16.1.1: icmp_seq=7 ttl=255 time=0.509 ms

ping: sendto: No route to host

ping: sendto: No route to host

Request timeout for icmp_seq 8

ping: sendto: No route to host

Request timeout for icmp_seq 9

ping: sendto: No route to host

Request timeout for icmp_seq 10

ping: sendto: No route to host

Request timeout for icmp_seq 11

Request timeout for icmp_seq 12

64 bytes from 172.16.1.1: icmp_seq=13 ttl=255 time=0.392 ms

64 bytes from 172.16.1.1: icmp_seq=14 ttl=255 time=0.358 ms

64 bytes from 172.16.1.1: icmp_seq=15 ttl=255 time=0.414 ms

64 bytes from 172.16.1.1: icmp_seq=16 ttl=255 time=0.435 ms

64 bytes from 172.16.1.1: icmp_seq=17 ttl=255 time=0.757 ms

ping: sendto: No route to host

ping: sendto: No route to host

Request timeout for icmp_seq 18

ping: sendto: No route to host

Request timeout for icmp_seq 19

ping: sendto: No route to host

Request timeout for icmp_seq 20

ping: sendto: No route to host

Request timeout for icmp_seq 21

ping: sendto: No route to host

Request timeout for icmp_seq 22

Request timeout for icmp_seq 23

Does this on both wired and WiFi on three different networks.

Without reliable network access I can’t do anything with my MBP including sending Apple feedback or downgrading the OS. It’s kind of bricked.

Any ideas would be greatly appreciated

Using my iPad to post this on the same network as the MBP.

Post not yet marked as solved Up vote post of MikePappas Down vote post of MikePappas
3.1k views
Posted by
MikePappas
Reply
Add a Comment

Replies

Is this the beta release that was released today?

Just a little jumpy about installing this after getting scorched with the 13.4 Beta (22F5059b)..

That being said this was the first time on many many years that a beta has "put me off the air".

Posted by
MikePappas
Post not yet marked as solved Up vote reply of MikePappas Down vote reply of MikePappas

  • Release from today 13.4 (22F62) doesn't have the issue anymore.

    —
    chuesler
Add a Comment

Any suggestions on how to upgrade without network connectivity? I have not found any identifiable network filtering apps, so I cannot get the software update download to complete. Is it possible to bring it over from another Mac via thumb drive?

Posted by
PDXAlex
Up vote reply of PDXAlex Down vote reply of PDXAlex

  • Start your Mac in Safe Mode - run the update from there.

    —
    chuesler
Add a Comment

Try looking under the "network tab" for the "filters tab" and if it has a green "active" indicator you have something running thats probably causing the problem. I have had those come back to life after turning them off multiple time and had to delete both WireGuard and Cisco Anyconnect to restore network access.

Posted by
MikePappas
Up vote reply of MikePappas Down vote reply of MikePappas

  • Thank you, Mike. That showed me an old copy of Sophos was running, even thought I "thought" I had uninstalled. Update is working now.

    —
    PDXAlex
Add a Comment

For me, it was LittleSnitch. Search the web for "uninstall littlesnitch" because it's not obvious. That gave me back my internet access. Updating to 13.4 (GA) now.

Posted by
Skyzyx
Up vote reply of Skyzyx Down vote reply of Skyzyx
Add a Comment

This issue still happens for me. With and without VPN, with both OpenVPN and Wireguard. With and without filtering (mostly with filters though, both LuLu and Little Snitch). On two different machines, M1 and M3. It's random.

If I have to bet, there's a deadlock caused by running x86 code on Arm hardware. As a software engineer I saw cases where Intel tolerates bad multI-threading more than Arm.

Are the Apple devs working on this? This is a very serious issue that makes these very expensive laptop unusable!

At least provide a way to reset the network stack!

Posted by
LostButFound
Up vote reply of LostButFound Down vote reply of LostButFound
Add a Comment