Jump to content
Corsair Community

Corsairlink4 using massive amount of background tcp requests???


Th3VVraith

Recommended Posts

What's the reason behind this? why is it polling at a ridiculous rate between internal TCP ports?

 

literally thousands of requests in a 2 minute timespan, receive and send...

 

what's going on?

 

I attached a "process monitor" screenshot... couldn't show entire list, as it would be impossible to do so via a text or log copy, it is an massive amount being logged every second.

 

red arrow indicates middle of output log... above that, there are several thousand requests, below it, several thousand more and continuously climbing... and just to give an idea of the realestate this screenshot covers, its a 4k monitor in use, screenshot is full screen at max res.

 

no other program on the system in question comes remotely close to the excessive background requests that "Corsairlink4.exe" is executing including the 24/7 streaming server set up on it.

 

Why is the question, what exactly is the software polling? (please, don't tell me its to "auto update" the software itself...)

link4excess.thumb.jpg.6711768d808bbc29594566da0bf753f7.jpg

Link to comment
Share on other sites

what's going on?

 

To me it looks like CorsairLink4.exe is using TCP to talk to the CLink4Service WIN32 service :eek:.

 

Looking at what TCP ports are open then the two CorsairLink4.exe TCP ports have a remote port of 8080 and if I stop the CLink4Service WIN32 service then the 8080 ports go away.

 

Maybe this also explains why CL4 uses vast amounts of CPU time :idea:.

 

attachment.php?attachmentid=24369&stc=1&d=1455750080

1765845109_TCPPorts.thumb.png.8416340defd920ec7c8b992be519cef4.png

Link to comment
Share on other sites

To me it looks like CorsairLink4.exe is using TCP to talk to the CLink4Service WIN32 service :eek:.

 

Looking at what TCP ports are open then the two CorsairLink4.exe TCP ports have a remote port of 8080 and if I stop the CLink4Service WIN32 service then the 8080 ports go away.

 

Maybe this also explains why CL4 uses vast amounts of CPU time :idea:.

 

I have yet to sniff the data being exchanged, but if this is the case, it's a lousy implementation of hardware control/monitoring, especially at the rate this is flooding the protocol stack... I'm unsure if I'll even be able to grab any data seeing how quickly the requests are being pushed through, just monitoring the actual requests is hard to keep up with; it's not like each request is a duplicate of another, each one is it's own unique request with it's own data payload, I have no idea what trying to sniff the data going back and forth will result in, or if the software will even be able to keep up without crashing...

 

Here's a screenshot of the info you requested. I hope it helps solve this confounding issue.

 

 

Doesn't clear much of anything up, and to think I came across this by accident while trying to figure out a streaming issue from the rig this is running on; coincidentally, it also resulted in me finding out why my hd cctv software refused to stream my cameras to this rig (receives on port 8080 by default... has since been changed and is now up and running... just laggy and stuttering/jumpy, like everything else I try to stream out from the rig.)

 

This is some heavy overhead on the tcp protocol, now to find out what exactly is being sent back and forth.

Link to comment
Share on other sites

but if this is the case, it's a lousy implementation of hardware control/monitoring, especially at the rate this is flooding the protocol stack.

 

It's CL what do you expect? As for it using port 8080 I feel this is a poor choice as it's the default for many proxy servers. From what I have seen I am 99% sure this is what is happening and your post was great as I would never have considered this as the data exchange regime otherwise.

 

I would be inclined to use Windows Pipes as I expect these have a lower overhead. There must be a reason for the CL4 CPU usage being 50% more than CL3 and suspect this may be one factor.

 

Here's a screenshot of the info you requested. I hope it helps solve this confounding issue.

 

Thank you, though it would have better to post this to in http://forum.corsair.com/forums/showthread.php?p=837702 as port 8080 already being used on your system was just a possibility as to why the CL4 service will not start.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...