Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > chi.internet > #3085

Re: IoT

From Bruce Esquibel <bje@ripco.com>
Newsgroups chi.internet
Subject Re: IoT
Date 2015-06-04 11:01 +0000
Organization Ripco Communications Inc.
Message-ID <mkpb6v$rfd$1@remote5bge0.ripco.com> (permalink)
References <MPG.2fd8fb526c56e96b989fab@news.speakeasy.net> <slrnmmue7d.bao.glg@ftupet.ftupet.com> <mknqhk$bu4$1@reader1.panix.com> <MPG.2fd94fed5952ccc8989fae@news.speakeasy.net>

Show all headers | View raw


Mark Anderson <mea@nospambradnylion.com> wrote:

> If I get ambitious I might let that TCP to 8.8.8.8 through for awhile  
> and see what it's doing.  Right now the firewall drops those packets 
> into a bit bucket with no response.  The camera just sends SYN and 
> that's it.  See how stupid you sound when you assume a situation?  Do 
> you always make proclamations on mere assumptions?  

> The repeated hammering of 8.8.8.8 and one other address set off an alarm 
> which is how I discovered that the camera was acting funny.  I never 
> expected a camera that has been operating 24/7 for 3 months flawlessly 
> would do this.

I think you answered your own question.

Although that iotcplatform.com site seems dead, it's probably why the camera
keeps trying to look up the ip data for it.

The iotc stands for "Internet of Things Cloud", and if you google around for
that, you get shit like this back:

-------------------------------------------------------------------
IOTC (Internet of Thing Cloud) Platform is a total solution for P2P
connections. It builds up a totally new concept of IOT connection platform
based on P2P (Point to Point) network connection architecture and advanced
Cloud computing technology via API (Application Programming Interface) for
cross-platform connection. Developers will be able to utilize ready-to-use
API to build up the connection between different devices or even across
different Operation Systems.

Until now, most of network devices connections are based on Dynamic IP, for
that reason, DDNS (Dynamic Domain Name Service) and Port mapping are
required for internet connection. It's too complicate for non-professional
users. As a result, the development progresses for the applications of
connecting to different IP devices are very limited, especially for consumer
markets.

Blah blah blah.
--------------------------------------------------------------------

I'm guessing the camera talked to the mothership on occasion to do
something, maybe each device the company made did that, in case you bought
two, they can talk to each other via the mothership rather than manually
being made aware each other exists or something.

Since iotcplatform.com is going to a godaddy holding page now, whatever they
were doing is gone or closed and the camera is just trying to get through to
something that doesn't exist.

My theory anyway.

I have something here at the house similar, think it's the Seagate NAS, when
it was configured it asked for an email address to send the alerts and
notifications to, but never asked for an smtp server, username, password or
anything else, just the address to send to. When it finally spat out a
message, it appears Seagate decided to hard code their shit into it, it
sends the message out to one of their servers and gets relayed from there to
me. No way to override that feature.

Of course one peice of stupidity to that way of doing things, one of the
messages it send out is "network is down", which of course means, if it's
sending out of the local network for smtp and there is no network, there is
no message sent.

-bruce
bje@ripco.com

Back to chi.internet | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: IoT Cydrome Leader <presence@MUNGEpanix.com> - 2015-06-03 21:11 +0000
  Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-03 18:55 -0400
    Re: IoT Bruce Esquibel <bje@ripco.com> - 2015-06-04 11:01 +0000
      Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-04 14:49 -0400
        Re: IoT Bruce Esquibel <bje@ripco.com> - 2015-06-05 12:02 +0000
          Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-05 13:54 -0400
            Re: IoT Cydrome Leader <presence@MUNGEpanix.com> - 2015-06-05 18:07 +0000
              Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-05 14:10 -0400
              Re: IoT smr <me@shawnritchie.com> - 2015-06-05 13:13 -0500
                Re: IoT smr <me@shawnritchie.com> - 2015-06-05 19:34 -0500
                Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-05 22:37 -0400
                Re: IoT Geoff Gass <glg@tanzenmb.com> - 2015-06-06 04:43 +0000
                Re: IoT Cydrome Leader <presence@MUNGEpanix.com> - 2015-06-08 16:55 +0000
                Re: IoT smr <me@shawnritchie.com> - 2015-06-08 14:14 -0500
                Re: IoT smr <me@shawnritchie.com> - 2015-06-06 15:02 -0500
                Re: IoT Cydrome Leader <presence@MUNGEpanix.com> - 2015-06-08 16:57 +0000
                Re: IoT smr <me@shawnritchie.com> - 2015-06-08 16:16 -0500
                Re: IoT Cydrome Leader <presence@MUNGEpanix.com> - 2015-06-09 21:58 +0000
                Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-09 18:48 -0400
    Re: IoT Cydrome Leader <presence@MUNGEpanix.com> - 2015-06-04 19:16 +0000
      Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-04 15:50 -0400
        Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-04 19:18 -0400
          Re: IoT Cydrome Leader <presence@MUNGEpanix.com> - 2015-06-04 23:47 +0000
            Re: IoT Mark Anderson <mea@nospambradnylion.com> - 2015-06-05 14:07 -0400

csiph-web