linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Remote IP setup of devices in a network
Date: Wed, 09 Nov 2011 00:59:38 +0000	[thread overview]
Message-ID: <1320800378.1926.0.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20111108193158.GA28261@merkur.ravnborg.org>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

On Tue, 2011-11-08 at 20:31 +0100, Sam Ravnborg wrote:
> 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.

Note that to use *link-local* IPv6 you don't need any co-operation from
infrastructure. You don't need global routing; you don't need to be
generally operating in 21st century conditions. If you have an
Ethernet-like link between your devices, link-local IPv6 should work
fine.

-- 
dwmw2



[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5818 bytes --]

  parent reply	other threads:[~2011-11-09  0:59 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
2011-11-08 23:30     ` Eliot Blennerhassett
2011-11-09  0:59     ` David Woodhouse [this message]
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=1320800378.1926.0.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=sam@ravnborg.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 NNTP newsgroup(s).