[Buildroot] ping and nslookup doesn't work on device

[Buildroot] ping and nslookup doesn't work on device

[Kantanu Kumar Mohapatra]

Hi All,

I am using an ARM 926EJS target board with buildroot-2014.02 to build the
code.
I am running linux-2.6.39 kernel.

Ping and nslookup not working on my device.

# ping google.com
ping: *bad address 'google.com <http://google.com/>'*

# ping 192.168.1.104
PING 192.168.1.104 (192.168.1.104): 56 data bytes
64 bytes from 192.168.1.104: seq=0 ttl=64 time=3.657 ms
64 bytes from 192.168.1.104: seq=1 ttl=64 time=0.402 ms
64 bytes from 192.168.1.104: seq=2 ttl=64 time=0.366 ms
--- 192.168.1.104 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.366/1.475/3.657 ms

# nslookup google.com
nslookup: *can't resolve 'google.com <http://google.com/>*'

Can anyone please say, what should I add in busybox-config (packages),
linux-config and busybox-config to solve this issue.

Thanks,
Kantanu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141126/b817be28/attachment.html>

[Buildroot] ping and nslookup doesn't work on device

[Thomas Petazzoni]

Dear Kantanu Kumar Mohapatra,

On Wed, 26 Nov 2014 20:01:50 +0530, Kantanu Kumar Mohapatra wrote:

> I am using an ARM 926EJS target board with buildroot-2014.02 to build the
> code.
> I am running linux-2.6.39 kernel.
> 
> Ping and nslookup not working on my device.
> 
> # ping google.com
> ping: *bad address 'google.com <http://google.com/>'*
> 
> # ping 192.168.1.104
> PING 192.168.1.104 (192.168.1.104): 56 data bytes
> 64 bytes from 192.168.1.104: seq=0 ttl=64 time=3.657 ms
> 64 bytes from 192.168.1.104: seq=1 ttl=64 time=0.402 ms
> 64 bytes from 192.168.1.104: seq=2 ttl=64 time=0.366 ms
> --- 192.168.1.104 ping statistics ---
> 3 packets transmitted, 3 packets received, 0% packet loss
> round-trip min/avg/max = 0.366/1.475/3.657 ms
> 
> # nslookup google.com
> nslookup: *can't resolve 'google.com <http://google.com/>*'

Do you have valid things in /etc/resolv.conf ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] ping and nslookup doesn't work on device

[Kantanu Kumar Mohapatra]

Thanks Thomas.

This is resolv.conf in my device.

# cat /etc/resolv.conf
; DNS configuration
search private_domain
nameserver 223.1.4.3
nameserver 8.8.8.8
#
# ping 223.1.4.3
PING 223.1.4.3 (223.1.4.3): 56 data bytes
ping: sendto: Network is unreachable
#
# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: Network is unreachable
#

The resolve.conf is same for one of my buildroot-201.05 device, which is
able to ping and do nslookup.

Thanks,
Kantanu

On Thu, Nov 27, 2014 at 2:31 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Kantanu Kumar Mohapatra,
>
> On Wed, 26 Nov 2014 20:01:50 +0530, Kantanu Kumar Mohapatra wrote:
>
> > I am using an ARM 926EJS target board with buildroot-2014.02 to build the
> > code.
> > I am running linux-2.6.39 kernel.
> >
> > Ping and nslookup not working on my device.
> >
> > # ping google.com
> > ping: *bad address 'google.com <http://google.com/>'*
> >
> > # ping 192.168.1.104
> > PING 192.168.1.104 (192.168.1.104): 56 data bytes
> > 64 bytes from 192.168.1.104: seq=0 ttl=64 time=3.657 ms
> > 64 bytes from 192.168.1.104: seq=1 ttl=64 time=0.402 ms
> > 64 bytes from 192.168.1.104: seq=2 ttl=64 time=0.366 ms
> > --- 192.168.1.104 ping statistics ---
> > 3 packets transmitted, 3 packets received, 0% packet loss
> > round-trip min/avg/max = 0.366/1.475/3.657 ms
> >
> > # nslookup google.com
> > nslookup: *can't resolve 'google.com <http://google.com/>*'
>
> Do you have valid things in /etc/resolv.conf ?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141127/5aeefe0f/attachment.html>

[Buildroot] ping and nslookup doesn't work on device

[Thomas Petazzoni]

Dear Kantanu Kumar Mohapatra,

On Thu, 27 Nov 2014 12:59:12 +0530, Kantanu Kumar Mohapatra wrote:

> This is resolv.conf in my device.
> 
> # cat /etc/resolv.conf
> ; DNS configuration
> search private_domain
> nameserver 223.1.4.3
> nameserver 8.8.8.8
> #
> # ping 223.1.4.3
> PING 223.1.4.3 (223.1.4.3): 56 data bytes
> ping: sendto: Network is unreachable
> #
> # ping 8.8.8.8
> PING 8.8.8.8 (8.8.8.8): 56 data bytes
> ping: sendto: Network is unreachable

Well, if you can't reach the DNS servers, then there is no way for DNS
resolution to work. Your network configuration seems to be incorrect.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] ping and nslookup doesn't work on device

[Kantanu Kumar Mohapatra]

Thanks Thomas, I have solved the issue by adding iproute2 package to my
buildroot. This gives "tc" and "ip" binary. We have used avahi package
which was using "ip" binary from iproute2 package.

Thanks,
Kantanu
On 28-Nov-2014 12:13 AM, "Thomas Petazzoni" <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Kantanu Kumar Mohapatra,
>
> On Thu, 27 Nov 2014 12:59:12 +0530, Kantanu Kumar Mohapatra wrote:
>
> > This is resolv.conf in my device.
> >
> > # cat /etc/resolv.conf
> > ; DNS configuration
> > search private_domain
> > nameserver 223.1.4.3
> > nameserver 8.8.8.8
> > #
> > # ping 223.1.4.3
> > PING 223.1.4.3 (223.1.4.3): 56 data bytes
> > ping: sendto: Network is unreachable
> > #
> > # ping 8.8.8.8
> > PING 8.8.8.8 (8.8.8.8): 56 data bytes
> > ping: sendto: Network is unreachable
>
> Well, if you can't reach the DNS servers, then there is no way for DNS
> resolution to work. Your network configuration seems to be incorrect.
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141128/332fed4c/attachment.html>