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

Groups > comp.arch.embedded > #31999

Re: Configure network of an embedded device

From Dimiter_Popoff <dp@tgi-sci.com>
Newsgroups comp.arch.embedded
Subject Re: Configure network of an embedded device
Date 2023-09-05 13:43 +0300
Organization TGI
Message-ID <ud70pg$1ui7c$1@dont-email.me> (permalink)
References <ud6pcn$1sdej$1@dont-email.me>

Show all headers | View raw

On 9/5/2023 11:37, pozz wrote:
> Nowadays many Internet connected embedded devices are controlled by an 
> external proprietary cloud service (for example Sonoff[1] or Shelly[2]). 
> The installation in the final destination is very simple to the end user 
> that ignores completely all the technical issues:
> 
> 1. connect the device to the local Ethernet network (WiFi is slightly 
> more complex)
> 2. pair his mobile app to the device (QR code or serial number)
> 3. start configuring and using
> 
> Most probably the device works with DHCP client enabled, hoping to find 
> a DHCP server on the network and receive a suitable IP address to make 
> outcoming connection to the Cloud server. This happens in 99.99% of 
> cases and the user is super happy.
> 
> In other situations, if the gadget features a small/big display, the 
> advanced user could enter a network configuration menu and set the 
> desired configuration (DHCP or fixed IP address). This happens for 
> desktop PCs or tablets or similar gadgets (even if the user keeps most 
> of the time the DHCP default configuration).
> 
> I'm designian't beng a small embedded device that hasn't a display and c 
> controlled by a cloud system. It will be controlled on the local network 
> through a simple web browser pointed to the IP address of the gadget. 
> Indeed, a web server runs in the device.
> 
> I'm thinking to start with a fixed IP address, for example 
> 192.168.1.123. In 90% of cases the IP address can be used immediately 
> (written on a label on the gadget or in the quick start guide) and the 
> user could access the web page pointing the web browser to 
> 192.168.1.123. In cases where the local network isn't 192.168.1.x, the 
> user should use a PC configured temporarily with a compatible IP address 
> (192.168.1.124), access the web page and change the network configuration.
> 
> The problem happens when the user wants to install several devices on 
> the same network, for example 10 devices. Even if the network is 
> compatible (192.168.1.x) with the default fixed IP address 
> (192.168.1.123), he should connect one device at a time and change its 
> configuration before connecting another device to avoid IP addresses 
> conflicts.
> 
> So I'm wondering if there's a standard or quasi-standard way to manage 
> network configuration of devices on the same LAN.
> 
> The situation isn't so uncommon. IPCams are network oriented devices 
> that can be controller by a Cloud service from the manufacturer, but 
> mainly from a web page. It usually happens that more than one IPCam are 
> installed on the same LAN.
> 
> For example, Dahua IPCams usually start with the fixed IP address 
> 192.168.1.108. They have a software (Config Tool) that can be used[3] to 
> manage network configuration of multiple IPCams, even if they are 
> installed at the same time with the default IP address 192.168.1.108.
> 
> Is it a proprietary solution that uses only Ethernet frames (MAC 
> addresses) and not IP packets? Is it a well known protocol that I don't 
> know?
> 
> 
> 
> [1] https://sonoff.tech/
> [2] https://www.shelly.com/en-gb
> [3] https://www.youtube.com/watch?v=NIiI1BIHfms


I had the same issue some 15 years ago and I think I posted a similar
question here. Back then the "IoT" phrase was not invented, so I am not
sure if our netmca belongs... :) ( http://tgi-sci.com/tgi/nmca3.htm )

Anyway, the world has not changed much since, same issue same possible
remedies.
My initial one - which is still active on our devices - was to post
the IP address on a specific web address under our domain once the
device boots (it does so via ftp to a dedicated account we have
for that); the address contains the device serial number which
makes it specific, the user can locate it using a browser.

Nobody uses it. They all call before they even try to use that.

So we started shipping a router with each device; the router is set
to give fixed IP addresses to each of the devices we ship to
that customer (sometimes they are more than one).
This has worked fine. Even if they try to stray from the router
we have shipped they can verify things work with it and dig
further themselves, look for help locally etc.

======================================================
Dimiter Popoff, TGI             http://www.tgi-sci.com
======================================================
http://www.flickr.com/photos/didi_tgi/

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Configure network of an embedded device pozz <pozzugno@gmail.com> - 2023-09-05 10:37 +0200
  Re: Configure network of an embedded device Dimiter_Popoff <dp@tgi-sci.com> - 2023-09-05 13:43 +0300
    Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 11:03 -0700
  Re: Configure network of an embedded device Theo <theom+news@chiark.greenend.org.uk> - 2023-09-06 21:56 +0100
    Re: Configure network of an embedded device pozz <pozzugno@gmail.com> - 2023-09-07 09:54 +0200
      Re: Configure network of an embedded device Theo <theom+news@chiark.greenend.org.uk> - 2023-09-07 19:40 +0100
        Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 13:19 -0700
        Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 13:30 -0700
          Re: Configure network of an embedded device Dimiter_Popoff <dp@tgi-sci.com> - 2023-09-08 00:14 +0300
            Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 14:31 -0700
              Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 14:34 -0700
              Re: Configure network of an embedded device Dimiter_Popoff <dp@tgi-sci.com> - 2023-09-08 00:53 +0300
                Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 15:21 -0700
                Re: Configure network of an embedded device Dimiter_Popoff <dp@tgi-sci.com> - 2023-09-08 02:05 +0300
                Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 16:55 -0700
                Re: Configure network of an embedded device Dimiter_Popoff <dp@tgi-sci.com> - 2023-09-08 04:26 +0300
                Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 18:57 -0700
          Re: Configure network of an embedded device Theo <theom+news@chiark.greenend.org.uk> - 2023-09-08 10:17 +0100
            Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-08 03:20 -0700
  Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-07 10:57 -0700
    Re: Configure network of an embedded device pozz <pozzugno@gmail.com> - 2023-09-08 09:41 +0200
      Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-08 03:50 -0700
        Re: Configure network of an embedded device pozz <pozzugno@gmail.com> - 2023-09-08 13:56 +0200
          Re: Configure network of an embedded device Don Y <blockedofcourse@foo.invalid> - 2023-09-08 09:45 -0700
            Re: Configure network of an embedded device George Neuner <gneuner2@comcast.net> - 2023-09-08 16:50 -0400

csiph-web