• November 01, 2024, 03:27:17 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: unwanted connection on the NAS DNS-320L  (Read 5259 times)

pierre.huybens

  • Level 1 Member
  • *
  • Posts: 16
unwanted connection on the NAS DNS-320L
« on: January 09, 2014, 01:53:00 AM »

I have the following connection established  from my  DNS320L  the netstat shows:
 
tcp        0      0 192.168.1.201:37989     54.194.162.61:443       ESTABLISHED

  using lsof we can find that the connection is established  by the signalc  process

signalc    7100            root    4u     IPv4    2398399      0t0     TCP MyNas:37989->ec2-54-194-162-61.eu-west-1.compute.amazonaws.com:443 (ESTABLISHED)
does some one knows what this process is doing  ?
the process is running from  /mydlink  directory.
If I stop it, a few second after it is restarted
If this is to access the NAS from the outside network , could we disable this feature ?

where could we found more technical inforation about process running on the NAS  ?

thanks



Logged

tudvari

  • Level 1 Member
  • *
  • Posts: 18
Re: unwanted connection on the NAS DNS-320L
« Reply #1 on: January 10, 2014, 07:58:11 AM »

Hi.

I think this is a trojan or something like this. Unfortunately you should make a factory reset.

Regards,
tudvari
Logged

NixZero

  • Level 2 Member
  • **
  • Posts: 66
Re: unwanted connection on the NAS DNS-320L
« Reply #2 on: January 10, 2014, 10:49:24 AM »

I have the following connection established  from my  DNS320L  the netstat shows:
 
tcp        0      0 192.168.1.201:37989     54.194.162.61:443       ESTABLISHED

  using lsof we can find that the connection is established  by the signalc  process
west-1.compute.amazonaws.com:443 (ESTABLISHED)
that compute.amazonaws.com is pretty clear: its the connection to your cloud storage service on amazon cloud.
Logged

JavaLawyer

  • BETA Tester
  • Level 15 Member
  • *
  • Posts: 12190
  • D-Link Global Forum Moderator
    • FoundFootageCritic
Re: unwanted connection on the NAS DNS-320L
« Reply #3 on: January 11, 2014, 04:26:38 AM »

that compute.amazonaws.com is pretty clear: its the connection to your cloud storage service on amazon cloud.

While I'm not convinced this is connection is anything malicious, I'm not sure I entirely agree with your conclusion. D-Link Cloud camera owners have been reporting that same connection on their Cloud cameras dating back to 2012. D-Link does not offer Cloud-based storage for video feeds. Perhaps D-Link is partnering with Amazon in some other capacity relating to mydlink.

???  :-\  ???
« Last Edit: January 11, 2014, 04:30:13 AM by JavaLawyer »
Logged
Find answers here: D-Link ShareCenter FAQ I D-Link Network Camera FAQ
There's no such thing as too many backups FFC

pizzaking

  • Level 2 Member
  • **
  • Posts: 34
Re: unwanted connection on the NAS DNS-320L
« Reply #4 on: January 11, 2014, 05:06:19 AM »

While I'm not convinced this is connection is anything malicious, I'm not sure I entirely agree with your conclusion. D-Link Cloud camera owners have been reporting that same connection on their Cloud cameras dating back to 2012. D-Link does not offer Cloud-based storage for video feeds. Perhaps D-Link is partnering with Amazon in some other capacity relating to mydlink.

???  :-\  ???

I think you may be right. As far as i understand, the mydlink app does not require any port forwarding on the users network equipment, which must ultimately mean, that you do not have a direct connection to your DNS-320L when you use the mydlink app. My guess is that Amazon act as a routingserver in this connection, in the same way as when using TeamViewer for remote technical support.
Logged

pierre.huybens

  • Level 1 Member
  • *
  • Posts: 16
Re: unwanted connection on the NAS DNS-320L
« Reply #5 on: January 11, 2014, 07:53:48 AM »

This is not a virus. This should be part of the base software provide.  Currently my NAS is only accessible from my local LAN no port forwarding and I have only  install fun_plug.

The processes ( signalc  tsa ) and the watch dog (/mydlink/mydlink-watch-dog.sh) of the network  processes are started at boot time  from the folder /mydlink. There is also a script to start/stop them.

It is easy for you to check if you have the same on your DNS320 with the latest firmware version.
 We should ask DLink what us the usage of those connection, because using this connection with root privilege … anything can be requested to the NAS.

Well of course I can stop them using fun_plug at boot time, but before I would prefer to know why they are started
 
Thanks for your help.
Logged