From: Sam Ravnborg <sam@ravnborg.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Remote IP setup of devices in a network
Date: Tue, 8 Nov 2011 20:31:58 +0100 [thread overview]
Message-ID: <20111108193158.GA28261@merkur.ravnborg.org> (raw)
In-Reply-To: <1320779474.5402.2.camel@shinybook.infradead.org>
On Tue, Nov 08, 2011 at 07:11:09PM +0000, David Woodhouse wrote:
> On Tue, 2011-11-08 at 19:54 +0100, Sam Ravnborg wrote:
> > The idea is to use an UDP broadcast to discover all devices,
> > and a similar UDP broadcast to configure the devices.
> > In the latter the MAC will be the key to address individual devices.
>
> You could almost be describing link-local IPv6. Each device
> automatically gets an IPv6 address based on its MAC address, which you
> can use for unicast addressing. The broadcast (or multicast) bit is easy
> enough too.
We are forced to use a IPv4 network where we need to keep the devices
in the same network as a potential router.
So to describe the idea with a little drawing:
Host PC Device-1 Device-2
| | |
|---- DISCOVER----->|----------->|
| | |
|<-- REPLY(MAC:IP)--| |
|<-- REPLY(MAC:IP)---------------|
| | |
(technician manually decide IP setup)
| | |
|-- CONFIG(MAC:IP)->| |
|-- CONFIG(MAC:IP)-------------->|
The discover is maybe sent twice due to packer drops.
The Reply is sent once and may look like this:
MAC=01:02:03:04:05:06;IP=10.11.12.13;NM=255.0.0.0;GW=10.0.0.1;XX="foo bar";YY="baz buz"
The technician then decides the new config (or computer assisted).
And the CONFIG may look like this:
MAC=01:02:03:04:05:06;IP=192.168.0.201;NM=255.255.255.0;GW=192.168.0.1
I cannot get this with auto-IP or wahtever it is named for IPv4.
Sam
next prev parent reply other threads:[~2011-11-08 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 18:54 Remote IP setup of devices in a network Sam Ravnborg
2011-11-08 19:11 ` David Woodhouse
2011-11-08 19:31 ` Sam Ravnborg [this message]
2011-11-08 23:30 ` Eliot Blennerhassett
2011-11-09 0:59 ` David Woodhouse
2011-11-09 10:11 ` Martyn Welch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111108193158.GA28261@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=dwmw2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).