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
3k views
Posted by
MikePappas
Reply
Add a Comment

Replies

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

Posted by
barthansiva
Post not yet marked as solved Up vote reply of barthansiva Down vote reply of barthansiva
Add a Comment

Glad it’s just not me!

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

Same here: apsd connection rejected

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

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.

Posted by
wjpjr
Post not yet marked as solved Up vote reply of wjpjr Down vote reply of wjpjr
Add a Comment

Wow

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

Can’t post anything

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

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

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

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.

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

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

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

  • I also removed Cisco's AnyConnect VPN and all seems to be well. Anyconnect has filters that Apple is likely conflicting with.

    —
    flytripper

  • Also having this issue. And I need Cisco Anyconnect installed for work. And I can’t even reach the Apple Update server so not sure how I’m going to get a fix.

    —
    dherg

  • dherg You can disable the filters without completely uninstalling AnyConnect from the Network control panel. Under Filters change the first 2 to "Disabled" and close the window - important because the values appear to revert as the network connection bounces up and down. You may need to do the same again after a restart. With this you should be able to reach the update servers for when a fix becomes available!

    In my experience so far AnyConnect is otherwise useless until this is addressed.

    —
    bcampbellpd
Add a Comment

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

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

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. :)

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

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.

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

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

Posted by
Kms2223
Post not yet marked as solved Up vote reply of Kms2223 Down vote reply of Kms2223
Add a Comment

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.

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

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

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

  • Same, updated and all appears good again.

    —
    dherg

  • How did you get htis update. Mine says it's all up to date!

    —
    AllenJC
Add a Comment