Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eial Czerwacki <eial@scalemp.com>
To: buildroot@busybox.net
Subject: [Buildroot] ping not working in a glibc based buildroot
Date: Wed, 09 Jul 2014 17:40:18 +0300	[thread overview]
Message-ID: <53BD5452.6030902@scalemp.com> (raw)
In-Reply-To: <20140709142242.GK3003@tarshish>

Greetings Baruch

On 07/09/2014 05:22 PM, Baruch Siach wrote:
> Hi Eial,
>
> On Wed, Jul 09, 2014 at 04:28:53PM +0300, Eial Czerwacki wrote:
>> Greetings,
>>
>> I've built a root using buildroot-2014.05 with busybox and glibc.
>> after that I've mounted the image and chroot into it. I've tried to ping
>> my desktop and I get this:
>> # ping eial
>> ping: bad address 'eial'
>>
>> but when I'm trying the same from the host computer (where the image is
>> mounted) I get this:
>> [root at cluster1 ~]# ping eial
>> PING eial (10.100.0.120) 56(84) bytes of data.
>> 64 bytes from eial (10.100.0.120): icmp_seq=1 ttl=64 time=0.227 ms
>> 64 bytes from eial (10.100.0.120): icmp_seq=2 ttl=64 time=0.198 ms
>>
>> any ideas what can be the issue and how to solve it?
> This is most likely a name server configuration issue. Can you compare the 
> content of your host /etc/resolv.conf to that of your chroot?
>
> baruch
>
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?

Thanks,

Eial.

  reply	other threads:[~2014-07-09 14:40 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 [this message]
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
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=53BD5452.6030902@scalemp.com \
    --to=eial@scalemp.com \
    --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