holland11

Q: nsurlsessiond on Mac choking my internet by uploading a ton.

I had been getting 200-500 ping for hours at a time the last couple nights so I decided to take a look at my parent's computers to see if they had something going on.

 

They both have macs which I'm not very familiar with, but I opened up the Activity Monitor on my mom's Macbook during a high ping time and noticed she was uploadding between 500-1200kb/s which is our connections max.

 

The culprit of the uploading was 'nsurlsessiond'. I did some googling and found that it is often associated with the iCloud so I disabled iCloud (as far as I know anyways) and the uploading did not slow down.

 

I couldn't find anything on google about finding out what/where the data specific to my session of nsurlsessiond was going so I just used 4 lines in the terminal which I found on a few posts that closes nsurlsessiond until the next reboot.

 

So for now, my ping is stable but I'd like to be able to take a more permanent approach and maybe find out where all the data is coming from and where it is going. Both my parents are concerned with the whereabouts as well and they are convinced it is a virus sending their info.

 

Could someone give me some advice of how to go about getting to the bottom of this?

 

 

 

 

Another question that I have that is related is:

 

 

sudo ipfw pipe 1 config bw 55Mbit/s

sudo ipfw add 1 pipe 1 ip from any to any

 

 

I found this code online which essentially throttles your connection to a specific maximum speed.

 

 

What I want to know is: how can I set up separate speeds for download and upload?

 

And also if there is a way to use these commands to set a maximum upload speed to that specific program?

 

(the way I understand it, you can throttle specific ports so maybe if I found out which port the nsurlsessiond traffic was using, I could limit it with this)

 

Thank you!

 

TLDR: MacBook 10.10.5 has program 'nsurlsessiond' using up all of our upload and choking network. How can I dig deeper and find/fix the cause?

MacBook, OS X Yosemite (10.10.5)

Posted on Dec 14, 2015 9:50 PM