Menu
What's new
By:
Filters Better Search

Constantly getting kernel: TCP: time wait bucket table overflow on RT-AC68U

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

rkk2025

rkk2025

Occasional Visitor
Hi,
Lately my LAN seems to be collapsing every now and then. It usually ends with leaving me without internet for some minutes, or even makes it impossible to connect to the router itself (To the webpanel). The log gets usually spammed with "kernel: TCP: time wait bucket table overflow" during this time, which makes me believe it must be related to this.

Here is a longer Log extract, in case it would be any helpful:
...
Apr 23 14:09:00 kernel: net_ratelimit: 39 callbacks suppressed
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:00 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: net_ratelimit: 282 callbacks suppressed
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:16 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: net_ratelimit: 215 callbacks suppressed
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:26 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: net_ratelimit: 289 callbacks suppressed
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:31 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:41 kernel: net_ratelimit: 182 callbacks suppressed
Apr 23 14:09:41 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:41 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:41 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:42 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:42 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:42 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:42 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:42 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:42 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:42 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:46 kernel: net_ratelimit: 298 callbacks suppressed
Apr 23 14:09:46 kernel: TCP: time wait bucket table overflow
Apr 23 14:09:47 kernel: TCP: time wait bucket table overflow
...

Form what I understand this is due to too many simultaneous open or half open connections from the clients. But this also happened to me when only one or two clients were connected. Sometimes even only my mobile phone.

I did a netstat from the phone and I could observe that there are hundreds of half open connection made trough the Google Play services and Google Chrome. But would that be enough to collapse the whole network?

Today I had again the same LAN collapsing experience while I was using my computer. This time I did a netstat from the router and saw many connections coming from my computer:

tcp 0 0 192.168.2.1:35505 192.168.2.100:28619 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30751 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:29875 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26929 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28198 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26194 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26099 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31631 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:29916 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31851 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31507 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30639 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28875 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27916 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31589 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28240 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26183 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31525 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26079 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27845 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:29050 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27237 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27193 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27999 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31566 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30048 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31750 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28752 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:29924 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30202 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31492 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28779 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30798 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30223 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30099 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27735 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27140 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28238 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31092 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:29097 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:25930 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28672 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26205 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26095 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26816 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:26808 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27051 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:29910 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28136 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31481 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28972 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28788 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:30766 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31029 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:28158 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27261 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:29075 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:31472 TIME_WAIT
tcp 0 0 192.168.2.1:35505 192.168.2.100:27315 TIME_WAIT

And this is only the tcp part. The UDP part has around the same amount of open connections.

I left TCPView run on my Windows machine, revealing again that many of these connections come from Google Chrome. And it seems it is creating them and destroying them constantly, which makes me believe that the router may not be notified of the removal and keeps the list growing (But that's my wild guess here).

Anybody has an idea of what could be going on here?

EDIT: This is what is being shown in Sysinfo on the router. So there are still many free connections..
Connections 4752 / 300000 - 100 active
 
Last edited:
Interesting that it appears to be linked to something Chrome is doing.

The problem seems to be the rate at which the client's connections are created and discarded rather then the total number.

You could trying changing some kernel settings on the router but I think that's just trying to hide the underlying problem with Chrome. If you have ad-blocking on the router or some other customisation that might interfere with Chrome's ability to spy call home that might be the cause.
 
Could also be malware. I would start by checking installed add-ons.
 
Playing around with the results. I've restarted the router and was just browing the WebUI, and now there are tons of TIME_WAIT connections to the SSL port. It seems like for every resource the browser downloads, it creates a new port on the computer, connects to the server and once done it leaves the connection in TIME_WAIT mode. The same is happening when I'm accessing online web pages. Also add to this that Chrome is constantly scanning for Chromecasts in the network (Also via HTTP protocol) plus all the other services that come shipped with Windows 10 that keep making some online API calls, and the list keeps growing. But why are the connections not closed properly?

Here is another netstat extract:
tcp 0 0 192.168.2.1:443 192.168.2.100:23304 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23427 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23314 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23296 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23434 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23464 TIME_WAIT
tcp 0 0 192.168.1.250:38930 195.249.26.65:80 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23271 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23469 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23276 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23406 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23309 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23243 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23439 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23241 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23414 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23458 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23368 TIME_WAIT
tcp 517 0 192.168.2.1:443 192.168.2.100:23482 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23263 TIME_WAIT
tcp 0 6383 192.168.2.1:443 192.168.2.100:23481 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23298 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23244 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23384 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23398 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23393 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23343 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23436 TIME_WAIT
tcp 517 0 192.168.2.1:443 192.168.2.100:23486 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23247 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23355 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23467 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23403 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23450 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23278 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23329 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23425 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23249 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23371 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23462 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23387 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23346 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23353 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23313 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23386 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23225 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23273 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23258 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23394 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23383 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23351 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23224 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23333 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23432 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23375 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23441 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23347 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23228 TIME_WAIT
tcp 517 0 192.168.2.1:443 192.168.2.100:23484 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23310 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23306 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23385 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23284 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23246 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23227 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23373 TIME_WAIT
tcp 0 0 192.168.1.250:36658 195.249.26.41:80 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23388 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23256 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23280 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23408 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23401 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23334 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23335 TIME_WAIT
tcp 0 0 192.168.1.250:38927 195.249.26.65:80 ESTABLISHED
tcp 517 0 192.168.2.1:443 192.168.2.100:23483 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23460 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23295 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23336 TIME_WAIT
tcp 517 0 192.168.2.1:443 192.168.2.100:23485 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23330 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23253 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23261 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23223 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23453 TIME_WAIT
tcp 0 0 192.168.1.250:36660 195.249.26.41:80 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23455 TIME_WAIT
tcp 0 0 192.168.1.250:38934 195.249.26.65:80 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23316 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23259 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23294 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23359 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23396 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23357 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23282 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23473 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23221 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23423 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23292 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23332 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23350 TIME_WAIT
tcp 0 0 192.168.1.250:36663 195.249.26.41:80 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23370 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23303 TIME_WAIT
tcp 0 0 192.168.1.250:37865 195.249.26.65:80 ESTABLISHED
tcp 0 0 192.168.2.1:443 192.168.2.100:23305 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23245 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23242 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23320 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23257 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23372 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23416 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23226 TIME_WAIT
tcp 0 0 192.168.2.1:443 192.168.2.100:23222 TIME_WAIT
 
Ah. Looking a bit more carefully at your output... The connections are from your client to the router's web interface, not the internet.

I'm guessing that you're using the netstat tool in the router's Network Tools. I see the same sort of thing with my firmware although there are only about 42 connections (but they do keep changing).

So the question is, is the netstat output a red herring that is unrelated to your original problem?

Correction: the number of TIME_WAIT connections to the router varies between 40 and 80.
 
Last edited:
Not sure if this might be relevant or not, but I usually have many tabs open on both my PC and Mobile phone (From 50 to 100 at times -> Bad habit to avoid bookmarking everything). And each of them get saved, so whenever I start my computer all the tabs get loaded at once (They are probably mostly loading from cache, but may be also calling to the server to check for changes). The same goes on the phone, Chrome sometimes bugs out and scrolls over all the open tabs, probably contacting some if not all of the sites. This might create a burst of requests which may create those open sockets. But that only happens when I start my computer and open the browser for the first time, but the TCP Timeout issue can still happen randomly during the whole day, as if the system would never recover from the burst.

Just in case, to see if anything would change, I made the local port range bigger on the router, and reduced the close_wait time to 5. I'll report back when I see the log showing the overflow warning again.

Here is what I've run on the Router to increase the local port range (I couldn't find anything related in the WebUI):
echo "1025 61000" > /proc/sys/net/ipv4/ip_local_port_range
 
You might try increasing the number of buckets.

# cat /proc/sys/net/ipv4/tcp_max_tw_buckets
4096
 
So after several days I haven't had any issues yet. Increasing the Local Port Range and Buckets and reducing the close_wait time to 5 seems to have mitigated the issue for now.

I'm right now in another place, where we have a FritzBox router, which allows to see all automatically opened ports by UPnP, and here is where I'm starting to worry about my computer. It seems that every now and then the computer starts opening and closing UDP ports (Sometimes TCP) via UPnP. Most of the times it opens several ports and closes them all in the same second. Some open ports remain though. Now the most worying part is that I tried to find out what is opening this ports by using netstat -a -b or even scan my computer with nmap. But it seems that the ports are being opened and closed but no process ever listens on those ports, or are triggered by something I'm unaware of.

In the case of this being caused by a virus, I've let Bitdefender do a whole system scan, with no threats found.

Is there any way to see in Windows what process is doing UPnP calls? Though as far as I understand, UPnP is a http based protocol, so anybody can implement or craft some kind of curl based call or something to achieve the call. Any idea on how to tackle this issue?
 
You must log in or register to reply here.

Similar threads

M
Solved OpenVPN not working with UDP anymore; TCP works
Replies
7
Views
2K
Marc Aronson
M
RHPT
RT-AX88U constantly unable to see modem
Replies
8
Views
973
RHPT
RHPT
A
ROG Rapture GT-AX6000 cuts off wired connections, please help :(
2
Replies
21
Views
2K
zuub
Z
C
Loss of Internet and Red Light after a few days when one particular computer is on
Replies
16
Views
1K
cgrey8
C
N
Rt-ax88u pro Vs gt-ax11000 pro
Replies
4
Views
460
Nodar
N
Similar threads
Thread starter Title Forum Replies Date
M ASUS XT8 not getting IPv6 from WAN (using 5G modem) ASUS Wireless 1
Olndo Pindaro Best country to setup for getting the strong wifi signal. ASUS Wireless 14
P kernel: TCP: mptcp_fallback_infinite ASUS Wireless 1

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 902 (members: 30, guests: 872)
Top