This is a domain name resolution issue. You can verify that you can ping IP Addresses, ie 8.8.8.8 But you can't ping domain names, ie google.com
Does this sound like you? On Beaglebone running Debian, setting the nameserver or dns-nameservers directives in /etc/network/interfaces does NOT solve this problem. Writing nameserver 8.8.8.8 directive to /etc/resolv.conf does NOT solve this problem. Can't apt-get update (uses domain names, right), so you can't just reinstall a new DNS resolver. Reinstalling apt-get install resolvconf, if it successfully installs, still doesn't fix the problem. Setting the default gateway (/sbin/route add default gw 192.168.7.1) doesn't help... Here is the problem. dhclient needs to be running. Ensure you have at least one valid name server in your /etc/resolv.conf ie nameserver 8.8.8.8 Then run dhclient Then try to ping google.com root@sg1:~# ping google.com > > ping: unknown host google.com > > root@sg1:~# pico /etc/resolv.conf > > root@sg1:~# dhclient > > root@sg1:~# ping google.com > > PING google.com (172.217.0.46) 56(84) bytes of data. > > 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=1 ttl=55 > time=8.62 ms > > 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=2 ttl=55 > time=8.24 ms > > 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=3 ttl=55 > time=8.21 ms > > 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=4 ttl=55 > time=8.35 ms > > ^C > > --- google.com ping statistics --- > > 4 packets transmitted, 4 received, 0% packet loss, time 5531ms > > rtt min/avg/max/mdev = 8.214/8.360/8.625/0.161 ms > > root@sg1:~# > > > If this doesn't work for you, if you go back and check your /etc/resolv.conf file, you may notice that it's contents have changed. These settings are written to this file automatically from dhclient, often based upon what the DHCP server gives. And these settings come from your /etc/network/interfaces values. Verify that your networks DHCP server is serving the correct name server IP's and repeat your dhclient command. On Saturday, January 17, 2015 at 3:47:24 AM UTC-8, Raj_RB wrote: > > Hi, > > 1) I downloaded 'bone-debian-7.5-2014-05-14-2gb' (BBB eMMC flasher) from ' > http://beagleboard.org/latest-images' and the website given MD5 checksum > matched with my downloaded zip file. Then used Win32 Disk Imager (since > windows 7), for image writing 4GB microSD. > > 2) Inserted microSD into BBB and pressed the boot button and then applied > power using the power adapter. (Please note that I have not connected > Ethernet and USB cable for power during the whole flashing process). But > only power supply LED got lit and not the user LEDs for around 5 seconds. > Then I removed the power supply and while pressing the boot button, I > provided the power supply and then all LEDs got lit for an instance and > then the LEDs started to glow erratically. Within 20 mins all the User > LED were off and did not ON again as against the standard procedure in > which all LEDs must glow after successful flashing of eMMC. > > 3) So, I thought to see if this works and I removed the microSD and power. > Then I connected BBB with my PC (by USB) using putty (SSH). I was able to > login successfully into debian but I was not able to ping google after > adding new gateway (192.168.7.1) and changing nameserver to 8.8.8.8 in > '/etc/resolv.conf' file. > > Please note that before SSH-ing, I shared my wifi internet with BBB in > Network settings(Windows 7) and also I changed the IP address of my BBB to > 192.168.7.1. All this worked earlier for me by following this youtube link: > (https://www.youtube.com/watch?v=D-NEPiZDSx8). > > Also, BBB (Linux USB ethernet/ RNDIS gadget) in Network settings shows 'No > Internet access' eventhough I have shared internet and changed my ip > address to 192.168.7.1 with subnet mask 255.255.255.0 leaving the DNS > server addresses blank as in the youtube video. > > But now it doesn't work eventhough I have already done the same procedure > (flashing) many times now with the same result and feeling really > frustrated now. Please let me know if I am missing anything here. Is it due > to the flashing issue? > Waiting for all your inputs! Thank you!! > > > Output: > > BeagleBoard.org BeagleBone Debian Image 2014-05-14 > Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > [email protected] <javascript:>'s password: > Last login: Thu May 15 02:19:40 2014 from 192.168.7.1 > debian@beaglebone:~$ sudo su > root@beaglebone:/home/debian# route add default gw 192.168.7.1 > root@beaglebone:/home/debian# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 0.0.0.0 192.168.7.1 0.0.0.0 UG 0 0 0 usb0 > 192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0 > root@beaglebone:/home/debian# cat /etc/resolv.conf > domain localdomain > search localdomain > nameserver 192.168.1.1 > root@beaglebone:/home/debian# vim /etc/resolv.conf > root@beaglebone:/home/debian# cat /etc/resolv.conf > domain localdomain > search localdomain > nameserver 8.8.8.8 > root@beaglebone:/home/debian# ping http://www.google.com > ping: unknown host http://www.google.com > root@beaglebone:/home/debian# > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/4c3e2cec-390b-4c2a-8fe6-c44d5ab7d263%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
