On 16 March 2011 10:03, Michael Hudson-Doyle
<michael.hud...@canonical.com>wrote:

> On Tue, 15 Mar 2011 11:17:14 -0500, Paul Larson <paul.lar...@linaro.org>
> wrote:
> > > I like statically IP. How do we know which board would get which IP?
> > > One idea would be to set up a DNS for internal board names. e.g.
> > > panda01.internal.network would resolve to our preallocated static IP
> > > for board "panda01".
> > >
> > > This could then be used by the dispatcher to resolve the IP and pass
> > > it to the board through kernel cmdline.
> > >
> > > I hadn't really thought of passing it via cmdline.  If we need to bring
> it
> > up statically, we could possibly do that, or possibly just make the
> > necessary adjustments before booting the image.  What I was proposing, if
> > the image is already set up to dhcp by default, we could run a dhcp
> server
> > on the control node with the static ip assignments already in place for
> each
> > board.
>
> How would you do this?  Most boards don't have a fixed MAC address.  You
> can set up a dhcp-name but that (AIUI) means a different rootfs for each
> board and then you might as well just allocate a static IP...
>
> Also, some boards of the same type have the same MAC as well..



> > That way they always get the same address that we pre-allocated for
> > that board.  We'll also need to make sure that the control node has a
> valid
> > ip on both the internal and the external network.
>
> Cheers,
> mwh
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev
>



-- 
With warm regards,
Sachin
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to