Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #32005
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: Configure network of an embedded device |
| Date | 2023-09-07 13:19 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <uddb9e$3443p$2@dont-email.me> (permalink) |
| References | <ud6pcn$1sdej$1@dont-email.me> <TGs*FNJpz@news.chiark.greenend.org.uk> <udbvit$2t598$2@dont-email.me> <TGs*lzOpz@news.chiark.greenend.org.uk> |
On 9/7/2023 11:40 AM, Theo wrote: >> It's very strange there isn't any protocol at MAC level that manages IP >> configuration. MAC addresses are unique in the LAN and they could be >> discovered or printed on a label. >> With this protocol, you could connect and power up all the devices and >> use a simple software to manage network IP configurations. > > There is, it's called DHCP. Or IPv6 SLAAC, as below. As Don says, once > you've done DHCP everything is configured, but you either need to have a UI > to either the DHCP server or the device if you want to find out what > happened. For SOHO applications, one can likely gain access to the "clients list" in the DHCP server. But, that may not be the case in other scenarios (e.g., enterprise). It also ASSUMES you have a server running, locally (also common in SOHO). I've seen applications that would listen for broadcasts from "their" devices (recognized by OUI or content of the message packet) and present lists of these devices to the user. The user could then contact the device directly (through the application) to query (or modify) its configuration. But, this (IMO) *raises* the bar for casual users. You can also add some other "dedicated" point-to-point port on the device that you use to talk to *it* (before it sits on the wire). E.g., Cisco APs, APC UPSs, etc. all have such a "console" function. But, again, you now expect the user to be more tech savvy. A clever way of doing this for "one-off" units is to have a USB interface and present to the host as a mass storage device with an "autorun" that causes a *portable* app on the device to be invoked so the software is part of the device instead of needing to be "installed" on a phone, PC, etc. The app then presents a configuration interface for the user writing the configuration data back into the device (before being disconnected). [Perhaps a JS app could be more portable -- think Macs -- than a binary] The app could also give you a beachhead through which to install updates in the device (if over-the-wire updates become a problem). [I use an ethernet based version of this in my current design. A "dedicated" port allows for secure configuration of "new" devices prior to deployment. It lets me install firmware, secrets, configuration information, etc. -- as well as inventory the devices encountered, to date] > If it is specifically DNS you're interested in, there's mDNS, > which also does service discovery - connect a printer to the network and > it'll become available to devices like phones without any config; this is > because the printer responds to mDNS queries from phones, laptops, etc > saying what services it offers and the devices configure themselves > automatically (the printer also says it accepts certain standard formats > like raster or PDF so no need for drivers).
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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