Page 1 of 1

Orphaned AWS connections

PostPosted: Sat Feb 17, 2018 8:40 pm
by snowjay
Any idea what is causing the Indigo Plugin Host to have all these connections to AWS?

Code: Select all
IndigoPlu 175         jasone    8u  IPv4 0x081dff68      0t0  TCP 192.168.0.175:49999->52.70.30.52:443 (CLOSE_WAIT)
IndigoPlu 175         jasone   10u  IPv4 0x067cbf68      0t0  TCP 192.168.0.175:50000->54.174.104.176:9553 (CLOSE_WAIT)
IndigoPlu 175         jasone   26u  IPv4 0x081dfb58      0t0  TCP 192.168.0.175:49998->54.174.104.176:9553 (CLOSE_WAIT)
IndigoPlu 175         jasone   58u  IPv4 0x06a77748      0t0  TCP 192.168.0.175:49437->54.174.104.176:9553 (CLOSE_WAIT)
IndigoPlu 175         jasone   59u  IPv4 0x06f13788      0t0  TCP 192.168.0.175:49525->52.70.30.52:443 (CLOSE_WAIT)
IndigoPlu 175         jasone   60u  IPv4 0x06f09788      0t0  TCP 192.168.0.175:49633->54.174.104.176:9553 (CLOSE_WAIT)
IndigoPlu 175         jasone   61u  IPv4 0x06f2c338      0t0  TCP 192.168.0.175:49717->35.168.98.119:443 (CLOSE_WAIT)
IndigoPlu 175         jasone   62u  IPv4 0x04fda378      0t0  TCP 192.168.0.175:49875->52.87.80.95:443 (CLOSE_WAIT)


I'm not sure how long this has been going on, just started analyzing my traffic and noticed my firewall dropping connections to AWS due to being out of state.

Re: Orphaned AWS connections

PostPosted: Sun Feb 18, 2018 6:30 am
by snowjay
I do have the Nest Home plugin v2.0.50. I didn't realize Nest was on Amazon, that probably explains the traffic... still not sure why there are so many connections.

update:
I did verify it was Nest plugin. I disabled all plugins and rebooted. Then I started enabling them 1 by 1 leaving Nest for last. Only when it was enabled did the connections come back. Off to the plugins forum...