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

App & System Services Core OS
MikePappas OP
Created May ’23
Replies 20
Boosts 3
Views 3.2k
Participants 18

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.

Replies  20
Boosts  3
Views  3.2k
Participants  18
barthansiva OP
May ’23

I‘ve got exactly the same issue after this update. On my MBP 16 M1 Pro.

2
MikePappas OP
May ’23

Glad it’s just not me!

0
Mudganger OP
May ’23

Same here: apsd connection rejected

0
wjpjr OP
May ’23

If you are using any network content filters like Little Snitch, LuLu, etc. this is a known issue. Disabling the content filter is the only solution to restore normal network connectivity at the moment until Apple resolves the issue.

1
Mungkone OP
May ’23

Wow

0
MikePappas OP
May ’23

Can’t post anything

0
MikePappas OP
May ’23

Not running any blockers and turned off IP tracking and still have the problem.

0
MikePappas OP
May ’23

I was able to fix this problem. I found that Wireguard was running even with it being disconnected. I completely killed it and it fully resolved my problem. A big Thanks to everyone who commented on this thread.

2
larryInCincy OP
May ’23

I restored network functionality by removing Cisco's AnyConnect VPN.

1
Omaha2002 OP
May ’23

Had to deinstall Eset endpoint security to get the network starting again

0
dherg OP
May ’23

Having same issue since update. Believe I’m seeing issue because I have Cisco AnyConnect installed.

I know it’s beta but surprised on how an update can get out that completely borks the network stack. Live and learn I guess. Probably should bow out of the beta. :)

0
Foxtrot1 OP
May ’23

Having same issues, Removed my VPN platform however still had issues, removed content filtering and this resolved. Awaiting for Apple to released updated bug fix.

0
Kms2223 OP
May ’23

When can we expect the next beta release? These issues with networking are complete blockers.

1
MikePappas OP
May ’23

For unknown reasons WireGuard decided to reenable its self today which put my MBP right off the air. It would be really helpful if Apple could fix this sooner than later.

0
chuesler OP
May ’23

Just updated to Version 13.4 (22F62) and it looks like resolves the issue with the network filters.

1
MikePappas OP
May ’23

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".

1
PDXAlex OP
May ’23

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?

0
MikePappas OP
May ’23

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.

0
Skyzyx OP
May ’23

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.

0
LostButFound OP
Feb ’24

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!

0
Latest Ventura Beta 13.4 (22F5059b) has mangled network access
First post date Last post date
 
 
Q