All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego <diego.ml@zoho.com>
To: meta-freescale@yoctoproject.org
Subject: Re: static ip
Date: Thu, 16 Jul 2015 14:55:36 +0200	[thread overview]
Message-ID: <2833716.v7H5aENjJP@localhost.localdomain> (raw)
In-Reply-To: <CANdq1hJGsSgR83NxrTze-sSW=ZnuGB7pU_Q2sOSC0mb28d_xpA@mail.gmail.com>

> > After boot, this is what I can see with ifconfig eth0 command:
> > NO static ip is set on eth0 for inet
> > 
> > eth0      Link encap:Ethernet  HWaddr 00:04:9F:03:9F:FD
> > 
> >           inet6 addr: fe80::204:9fff:fe03:9ffd/64 Scope:Link
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:0 (0.0 B)  TX bytes:4642 (4.5 KiB)
> > 
> > However, if I execute:
> > /etc/init.d/networking restart
> > everything seems to work and I can connect to static ip
> > 
> > Any suggestion will be very appreciated.
> > Thank you in advance
> 
> it seems like /etc/init.d/networking is not executed at boot or
> executed when bad timing.
> 
> Wally

I experienced a similar timing problems some time ago, but with udhcpc, and I 
think this presented before:
https://lists.yoctoproject.org/pipermail/poky/2011-August/006931.html

So suggestion is to try waiting when the eth0 link is UP. I think there aren't 
obvious solutions to this, but there are several options you can try.

Bests,
Diego



  parent reply	other threads:[~2015-07-16 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  8:17 static ip Alvaro Martinez Tovar
2015-07-16  8:31 ` Wally Yeh
2015-07-16 10:03   ` Alvaro Martinez Tovar
2015-07-16 10:17     ` Wally Yeh
2015-07-17  0:24     ` Bob Cochran
2015-07-20  7:44       ` Alvaro Martinez Tovar
2015-07-16 12:55   ` Diego [this message]
2015-07-17  1:05 ` Hiromichi Matsumura
2015-07-20  7:31   ` Alvaro Martinez Tovar

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=2833716.v7H5aENjJP@localhost.localdomain \
    --to=diego.ml@zoho.com \
    --cc=meta-freescale@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.