[145153] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Synology Disk DS211J

daemon@ATHENA.MIT.EDU (Leo Bicknell)
Thu Sep 29 15:35:55 2011

Date: Thu, 29 Sep 2011 12:34:18 -0700
From: Leo Bicknell <bicknell@ufp.org>
To: "nanog@nanog.org" <nanog@nanog.org>
Mail-Followup-To: "nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <E36EB8E60B5EB244AAFCFEF0AF0A116D02FE359A34@MS-EX7MB-P03.corp.se.sempra.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

In a message written on Thu, Sep 29, 2011 at 12:11:48PM -0700, Jones, Barry=
 wrote:
> A little off topic, but wanted to share... I purchased a home storage Syn=
ology DS1511+. After configuring it on the home net, I did some captures to=
 look at the protocols, and noticed that the DS1511+ is making outgoing con=
nections to 59.124.41.242 (www) and 59.124.41.245 (port 81 & 89) on a regul=
ar basis. These addresses are owned by Synology and Chungwa Telecom in Taiw=
an.=20
>=20
> So far, I've not been able to find much information on their support site=
s, or Synology's wiki, but I wanted to put it out there.=20
>=20
> GET / HTTP/1.1
> Host: 59.124.41.245:81
> Accept: */*

Perhaps a little further digging was in order?  For instance, putting
the IP and port in a web browser (http://59.124.41.245:81) which
returns:

<html><head><title>Current IP Check</title></head><body>Current IP Address:=
 REDACTED</body></html>

Looking at Synology's web page we find:
http://www.synology.com/dsm/internet_connection.php?lang=3Dus

If they are going to do things like UPNP to open a port, and then DDNS
to let you get there from the outside world than the box needs to know
your outside NAT address, and simple relays like this are the best bet.
It's another ugly hack to get around the problems of a NAT in the
middle.  I bet the box also checks for a new version of software from
time to time.

While I would like vendors to better disclose the "phone home" behavior
of their devices, virtually every computing device does this in some way
or another if only to check for new software.  Windows and Mac's check a
web server to know if you are "connected to the internet" or not.  NAT
traversal often uses a relay.  DDNS registrations need the real IP, and
so on.

Not much to see here, really, other than how ugly some of our protocols
are in the real world.

--=20
       Leo Bicknell - bicknell@ufp.org - CCIE 3440
        PGP keys at http://www.ufp.org/~bicknell/

--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iQIVAwUBToTIOrN3O8aJIdTMAQLvVQ/+IHPN7JYnsGy9gaWBcAbPWiPGgno5AHQe
Iao5YGyQ1xMMd+dyqYO3eKdGrExkDWrHsOgut2AaQIrA8otQst2D9t9D5vBu8I8G
q9hqlPyWuwiSmSwZBQalFPfa8qdQudXo2dEKnZbJNTreTA2zz0M46bGHDkDqlkg+
cDMF2N/S9gaF2kps9ZpI2sYBaU3ym7oeY2OplksU+RXCD12+N/81lX9lFoIkd35N
sOei/QjqCsp8ozpzuI42RJpv8tefYqrK64b37f+qydzt7opRNKJm2B7rYH6qKUHa
sg9e6PAbfrDDmNlgqlpQLSFr+S27kaKFt4hjSgT3lo5I+yTGHSqf5WgZMLDWnGel
r4NMSWbu6q2UIDwCrJfaxXATuu6fgFWcP/W7g7ogDo6al1LWyD952g2W5KWzRgfI
GVeCEAhR4wOht5kqNgW7fJlr2zXZKXaN5lx4jELnId5AS4rZQ+Jwv97v/RSKs8nc
gUoaxaLCYNOAn2JETGfhhN/9C8mhClEzHyTFPAhtK2J2cAb90THv/V3egW04dRMf
2EWXuo7xEmTxmQ9Mor/d/ZEhOniCtJUwCcP/MYHq/Mi80Q823gRQZDQxxXas4egW
1x9GyPnyP1AAxI8OJ90oQa9anyIjExVMCZOTs0QfkD2yzA1XWLH8rGWctGYYOXPu
b4j8ECMUMyQ=
=qMHe
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--


home help back first fref pref prev next nref lref last post