----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> 5d8b5125
@REPLYADDR pozz <pozzugno@gmail.com>
@REPLYTO 2:5075/128 pozz
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@TZUTC: 0200
@PID: Mozilla/5.0 (Windows NT 10.0; Win64; x64;
rv:102.0) Gecko/20100101 Thunderbird/102.15.0
@TID: FIDOGATE-5.12-ge4e8b94
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
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.15.0
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441