----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> cff45821
@REPLY: 1@dont-email.me> 5d8b5125
@REPLYADDR Don Y <blockedofcourse@foo.invalid>
@REPLYTO 2:5075/128 Don Y
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References: 1@dont-email.me>
@TZUTC: -0700
@PID: Mozilla/5.0 (Windows NT 6.1; Win64; x64;
rv:102.0) Gecko/20100101 Thunderbird/102.2.2
@TID: FIDOGATE-5.12-ge4e8b94
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.
(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)
--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.2.2
* 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