Internet issues on Monterey

I have the exact same issue ever since I have upgraded my 2017 MBP to macOS Monterey

I have also tried everything described

I can also report that only rebooting the MAC or rebooting the Router will work to resolve. so thing suggests something related to dns negotiations or handshaking between MAC & Router.

Very annoying !!!

The DNS issues on Monterey are absolutely positively TERRIBLE. They are so bad I've been shopping for Chromebooks because I simply can not work on mac anymore. I have to constantly reboot now and constantly flush dns cache to get anything to work. I am so so sick of Apple and their garbage software at this point.

The answer is to change the setting on the router? I am using my mac in an enterprise setting where I do not have access to the router configurations. The Monterery is causing a huge headache with the internet connections and my productivity. I am a tech savvy person. This Monterey roll out was just a big fail in my book.

I experience the same issues immediately after upgrading to Monterey. The connection (wifi or Thunderbolt) dies after a few minutes of inactivity on the laptop. Restart so far is the only way to temporarily fix the connection. And then the connection dies again after a few minutes. Interestingly, on this very same laptop, when I run boocamp Windows, the connection has no issues. (Note, I have not upgraded my MacBookPro16,1 to Monterey because of the these issues)

My MacBook Pro spec:

Model Name: MacBook Pro

 Model Identifier: MacBookPro14,1

 Processor Name: Dual-Core Intel Core i5

 Processor Speed: 2.3 GHz

 Number of Processors: 1

 Total Number of Cores: 2

 L2 Cache (per Core): 256 KB

 L3 Cache: 4 MB

 Hyper-Threading Technology: Enabled

 Memory: 16 GB

 System Firmware Version: 447.40.12.0.0

 OS Loader Version: 540.40.4~45

 SMC Version (system): 2.43f11

Some info of running networking commands when the laptop gets into the bad state:

When MacBooK Pro has lost the internet connection:

$dig bbc.com

; <<>> DiG 9.10.6 <<>> bbc.com

;; global options: +cmd

;; connection timed out; no servers could be reached

$traceroute bbc.com

traceroute: unknown host bbc.com

After restarting the MacBooK Pro:

$dig bbc.com

; <<>> DiG 9.10.6 <<>> bbc.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17653

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;bbc.com. IN A

;; ANSWER SECTION:

bbc.com. 300 IN A 151.101.128.81

bbc.com. 300 IN A 151.101.192.81

bbc.com. 300 IN A 151.101.64.81

bbc.com. 300 IN A 151.101.0.81

;; Query time: 28 msec

;; SERVER: 2001:4e8:0:4009::11#53(2001:4e8:0:4009::11)

;; WHEN: Mon Dec 13 12:04:46 PST 2021

;; MSG SIZE rcvd: 100

$traceroute bbc.com

traceroute: Warning: bbc.com has multiple addresses; using 151.101.192.81

traceroute to bbc.com (151.101.192.81), 64 hops max, 52 byte packets

1 10.0.0.1 (10.0.0.1) 4.076 ms 1.646 ms 1.018 ms

2 ********* 9.823 ms 9.497 ms 9.598 ms

3 rc1st-be102-1.vc.shawcable.net (64.59.151.85) 10.825 ms 10.051 ms 14.987 ms

4 24.244.59.101 (24.244.59.101) 10.875 ms 12.245 ms 9.545 ms

5 rc1st-be214.vc.shawcable.net (24.244.58.65) 10.235 ms 9.599 ms 10.081 ms

6 rc2wt-be50-1.wa.shawcable.net (66.163.70.106) 16.275 ms 18.884 ms 14.432 ms

7 * * *

8 * * *

9 * * *

[Personal Information Edited by Moderator]

I was able to work this out with a senior technician at Apple (AFTER updating to 12.1 today).

After doing a million other steps the thing that got my speed back was by going to System Preferences > Network > Location, Edit Location > Hit the plus sign and add a location (I left it "untitled") then hit done.

It took a second for the ethernet/wifi to reconnect and turn green but when they did I ran my speed test which went from 0.09 mbps upload to 50.0 mbps

An interesting point was that the speed was normal (fast) in safe mode before I made these changes.

I hope this helps. Cheers.

This too worked for me (Creating a new Network location in System Preferences). I wish I better understood why it works, but I'm glad it works without rebooting.

I was able to switch back to automatic and everything worked again after that.

So I kept the second Location and called it Alternate. If this comes up again (and it's been coming up somewhat frequently lately), I'll see if switching back and forth will solve the issue.

Yesterday I performed a full uninstall on Cisco AnyConnect and reinstalled latest version (that my employer would provide, anyway) Version 4.10.03104

Also upgraded OSX to V12.2

I booted up my Readdle Spark application (email) and and got about 10 minutes of work until I lost Broadband connection as per usual. So 12.2 doesn't seem to solve it. I may try an uninstall of Cisco AnyConnect and see if that works...

Same old, same old... Not fun.

Best,

FightingIbis

I have been seeing this same issue, and to work around it I went into System Preferences -> Network and selected Cisco AnyConnect Socket Filter in the left hand pane (there are actually two instances of the Cisco AnyConnect Socket Filter and I chose the one that had a description of Please use “Cisco AnyConnect Socket Filter” to control this DNS proxy configuration). Then click the options pull down menu (the button that has three dots and a down arrow) and chose Make Service Inactive) then click the Apply button. After that, DNS service was restored. Will continue to monitor for reoccurrence.

I have the similar issue, My Mac dns resolver is broken every 3 days after upgrading to Monterey. the nslookup command shows the error:

nslookup www.google.com.tw

nslookup: isc_socket_bind: address not available

^^^^ Thanks for posting this! It appears this is "the fix" for me as well.

Once I made inactive the second (unused) instantiation of "Cisco AnyConnect Socket Filter" I have enjoyed no loss of DNS or Broadband connectivity for the last 24 hours. this is my longest unbroken connection since I installed Monterey OSX a couple of months ago.

I'll post with any further updates, but greatly appreciate all who contributed to this thread and all the diagnosis here.

My Best,

FightingIbis

In my case, I also noticed that after some period of time the problem may reoccur and I had to repeat the workaround. I'm guessing that my employer's remote management policy periodically does a check and re-activates the socket filter, so I had to go back into Network Preferences again to disable it. Seems to occur far less frequently now than before and at least it's preferable to the only other workaround I was aware of, which was a full reboot.

I can confirm this is the correct explanation.

The number of sockets in use can be monitored using Terminal: netstat -an | grep -e tcp -e udp | wc -l

Over the course of several hours and days, the reported number will gradually creep up until it reaches the default system limit of 16383, at which point a reboot is needed. In my case, the application that keeps opening all these sockets is com.cisco.anyconnect.macos.acsockext, which is the "Cisco AnyConnect Socket Filter Extension" that creates a new UDP socket for every DNS query originating from the systeem. Other applications may be culprits as well.

As you mentioned, the bug is not that AnyConnect creates these sockets, but rather that Monterey does not time these UDP sockets out after they have been used, which should typically be the case after 2 minutes (IIRC) inactivity. As a result, these old sockets keep lingering while new sockets continue to be created until eventually the resource is exhausted and a reboot is required. Monterey 12.1 does not yet fix this problem.

Do you have a Cisco bug number for this?

I didn't go into too much detail, but 16383 is the default ephemeral port range on macOS, which these sockets use. When you hit that number in ephemeral ports, you will have problems. You can have more than that number if those are ports outside the range.

In reality, the number produced by that Terminal command will be higher than 16383 before you run into problems, but in my case, only slightly. My system currently reports about 6000 sockets. The vast majority of those - more than 5000 - are lingering UDP sockets created by AnyConnect, each with an associated unique ephemeral port number, i.e., one of the 16383 possible ports.

93966 is pretty high; however, by removing the | wc -l at the end, you should be able to see the actual list. You can't have more than 65535 ports open in total, so there must be duplicates or thousands of *.* in there.

Hey, I also came to the same conclusion, for the people running/using Cisco AnyConnect that is the case, perhaps others that don't have AnyConnect but still are seeing this issue, then it should be another application with similar behaviour that causes the issue. We've been advised by Cisco that this is not Cisco AnyConnect bug/issue but macos. They have filed a bug report to Apple under FB9803355 bug. So far I've tested it with different Cisco AnyConnect versions but it is the same case even with the latest update 4.10.04071.