----------------------------------------------------------------------------------
@MSGID: 2@dont-email.me> b05b819d
@REPLY: 1@dont-email.me> cff45821
@REPLYADDR pozz <pozzugno@gmail.com>
@REPLYTO 2:5075/128 pozz
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 2@dont-email.me>
@RFC-References: 1@dont-email.me>
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
Il 07/09/2023 19:57, Don Y ha scritto:
> On 9/5/2023 1:37 AM, pozz wrote:
>> 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?
>
> RARP gave way to BOOTP which gave way to DHCP for exactly this reason.
>
> They all run *below* the IP layer so can be implemented (client-side)
> relatively easily. Assigning IP, hostname, gateway, nameserver,
> timeserver, boot server, boot image, etc. are all done, there.
Ok, but you can`t set a static IP address through DHCP and you are
forced to have an always on DHCP server on the LAN (maybe you don`t want
to have one for some reason).
If I wanted to have only static IP addresses on my LAN, I would be
forced to change the IP configuration on each device, through
proprietary mechanisms (display, web app, ...). And if you have 50 hosts
(IPCams?), it is a waste of time.
Anyway I think Dahua (and maybe other IPCams manufacturers) doesn`t use
DHCP to auto-configure IPCams connected to its NVRs. IPCam usually
starts by default with a unique static IP address (192.168.1.108).
If you have only one IPCam in the LAN, it`s very simple for the user as
pointing the browser to:
http://192.168.1.108.
If you have multiple IPCams, connect them to modern NVRs from the same
manufacturer and point the browser to the NVRs IP address. Through the
web interface of the NVR, the user can see all the IPCams (even if they
have the same IP address) and change their network configuration (DHCP
or static IP) one-by-one or all together (assigning a range of IP
address sequentially).
Even if you don`t have NVR, you can use Dahua Config Tool software. It
is able to discover and set network configuration of IPCams on the
LAN[1]. How are they able to do this?
I suspect this isn`t standard because someone said this works only if
NVR and IPCams are from the same manufacturer. Even Config Tool software
can discover IPCams only if they are Dahua.
I think this method is very simple for the user.
> (You can operate an ethernet without IP at all!)
>
> The problem is:
> - having a suitable server present on the network
> (not all will have this -- though most SOHOs will)
> - conveying the parameters that were assigned by
> the service to the *human* user (without requiring
> special knowledge of a special tool which would
> require more knowledge of the user`s operating
> environment *or* having a UI on the device)
>
[1]
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