From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] ping not working in a glibc based buildroot
Date: Thu, 10 Jul 2014 18:30:35 +0200 [thread overview]
Message-ID: <20140710163034.GC28300@free.fr> (raw)
In-Reply-To: <53BE83E8.2010906@scalemp.com>
Eial, All,
I know you solved your issue by copying the missing NSS libs,
yet I have a comment about this mail, see below.
On 2014-07-10 15:15 +0300, Eial Czerwacki spake thusly:
> On 07/09/2014 05:53 PM, Eial Czerwacki wrote:
> > Greetings Gustavo,
> >
> > On 07/09/2014 05:46 PM, Gustavo Zacarias wrote:
> >> On 07/09/2014 11:40 AM, Eial Czerwacki wrote:
> >>
> >>> yes, here it is:
> >>> --- /etc/resolv.conf 2014-07-09 17:35:30.420040438 +0300
> >>> +++ yyy/etc/resolv.conf 1970-01-01 02:00:00.000000000 +0200
> >>> @@ -1,3 +0,0 @@
> >>> -; generated by /sbin/dhclient-script
> >>> -search cluserdns cluserdnsus
> >>> -nameserver 10.100.1.40
> >>>
> >>> thing is, I'm not sure who generates the content of that file, is it
> >>> part of busybox? other utility?
> >> That depends on your network configuration, for static IP scenarios
> >> normally you do, for DHCP it's normally done by the dhcp post up script.
> >> Regards.
> >>
> >>
> >>
> > did you mean /usr/share/udhcpc/default.script?
> I've looked into the resolv.conf of the actual boot (not chroot) and I
> saw the domain bad issue (bug #3979), applying it gave me valid domain
> again in resolv.conf but problem still persists.
>
> it is like udhcpc cannot find the dns servers. am I right? where do we
> set dns?
When you are in a chroot, you are still using the IP stack from your
non-chroot system, so the network interfaces are already configured.
So, no need to run a DHCP client.
However, you still need to properly setup the resolver in your chroot,
which you did by filling in /etc/resolv.conf and copying the NSS libs.
For example, I usually just copy the non-chroot /etc/resolv.conf into my
chroot.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-07-10 16:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 13:28 [Buildroot] ping not working in a glibc based buildroot Eial Czerwacki
2014-07-09 14:22 ` Baruch Siach
2014-07-09 14:40 ` Eial Czerwacki
2014-07-09 14:46 ` Gustavo Zacarias
2014-07-09 14:53 ` Eial Czerwacki
2014-07-10 12:15 ` Eial Czerwacki
2014-07-10 12:23 ` Thomas Petazzoni
2014-07-10 12:35 ` Eial Czerwacki
2014-07-10 12:56 ` Thomas Petazzoni
2014-07-10 13:02 ` Eial Czerwacki
2014-07-10 13:34 ` Thomas Petazzoni
2014-07-10 13:40 ` Eial Czerwacki
2014-07-10 14:06 ` Thomas Petazzoni
2014-07-10 14:13 ` Eial Czerwacki
2014-07-10 14:16 ` Thomas Petazzoni
2014-07-10 14:25 ` Eial Czerwacki
2014-07-10 21:18 ` Yann E. MORIN
2014-07-10 14:24 ` Baruch Siach
2014-07-10 14:34 ` Eial Czerwacki
2014-07-10 16:30 ` Yann E. MORIN [this message]
2014-07-13 6:37 ` Eial Czerwacki
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=20140710163034.GC28300@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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