[beagleboard] Cannot ping google in BBB even after sharing internet

[Raj_RB]

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:

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
***@192.168.7.2's password:
Last login: Thu May 15 02:19:40 2014 from 192.168.7.1
***@beaglebone:~$ sudo su
***@beaglebone:/home/debian# route add default gw 192.168.7.1
***@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
***@beaglebone:/home/debian# cat /etc/resolv.conf
domain localdomain
search localdomain
nameserver 192.168.1.1
***@beaglebone:/home/debian# vim /etc/resolv.conf
***@beaglebone:/home/debian# cat /etc/resolv.conf
domain localdomain
search localdomain
nameserver 8.8.8.8
***@beaglebone:/home/debian# ping http://www.google.com
ping: unknown host http://www.google.com
***@beaglebone:/home/debian#

[Curt Carpenter]

Hello.

I had similar trouble with WinXP, and the problem I had included issues
with the way I had my Windows network configured. Win 7 is much different
though, so can't offer any help there. Otherwise, you may already be doing
this but just in case, I have the following lines in a script that I run
after I've booted my BBB:

#!/bin/sh
echo "Setting up the default gateway"
/sbin/route add default gw 192.168.7.1
# May need to run this if /etc/resolv.conf gets corrupted
#echo "Updating the nameserver entry"
echo "nameserver 8.8.8.8" >> /etc/resolv.conf

[Raj Bharath RB]

Hi Curt,

The thing is it actually worked earlier by following the already mentioned
youtube video even though the video is for Windows 8.

Actually, I am a newbie. Even I ran the same script but I am not sure
whether it was done in the correct file.

***@beaglebone:/home/debian# route add default gw 192.168.7.1
Will this above script make changes in the file *#!/bin/sh *as your script?

***@beaglebone:/home/debian# cat /etc/resolv.conf
domain localdomain
search localdomain
nameserver 8.8.8.8

Even I made changes like above in */etc/resolv.conf *file.
Do I need to change *localdomain* in the above script also?

Thanks Curt.

Post by Curt Carpenter
Hello.
I had similar trouble with WinXP, and the problem I had included issues
with the way I had my Windows network configured. Win 7 is much different
though, so can't offer any help there. Otherwise, you may already be doing
this but just in case, I have the following lines in a script that I run
#!/bin/sh
echo "Setting up the default gateway"
/sbin/route add default gw 192.168.7.1
# May need to run this if /etc/resolv.conf gets corrupted
#echo "Updating the nameserver entry"
echo "nameserver 8.8.8.8" >> /etc/resolv.conf
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the
Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/9PWK96YLkzA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
For more options, visit https://groups.google.com/d/optout.

[Gary McKinney]

Hi,

It appears you have done everything right but any little item missed will
stop the link from working properly.

There are several questions you need to ask yourself...

Except where stated otherwise all the tests below are performed from the
BeagleBone system.

1. Does ifconfig command show the correct information for the usb0
interface?

2. Can you ping the ip address assigned to the usb0 interface (192.168.7.2)?
If not then there is something not configured properly on your usb0
interface. Check the /etc/network/interfaces file to make sure the entry
for usb0 is correct.

3. Can you ping the ip address of the PC's link interface (192.168.7.1)?
If you can not ping the PC link interface address then there is
something incorrectly configured on that interface - double check the
interface settings to make sure the assigned IP address & netmask address
is set correctly.

4. From the PC can you ping the link interface (192.168.7.1)?
If not there is something wrong with the link interface configuration.

5. From the PC can you ping the BeagleBone usb0 interface (192.168.7.2)?
If not double-check the usb0 interface configuration in
/etc/network/interfaces and look at the "ifconfig usb0" command results for
any discrepancies.

6. Can you ping the PC's network bridged IP address (the interface you have
bridged over to the usb link interface on the PC)?
If not make sure you have the bridging setup properly on the PC
interfaces.

7. Can you ping the PC's default gateway IP address?

If everything is reachable (pingable) up to this point then it has to be
something in the resolver settings (DNS).

Double check to make sure the /etc/resolv.conf file has the proper DNS
server entry so you can resolve FQDN names (those listed in DNS that is).

It has been my experience when network issues crop up they tend to be
something simple but over looked if things had previously worked before
something was changed.

Hopefully the above helps. Let us know what you find :)

gm...

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
http://youtu.be/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!!
BeagleBoard.org BeagleBone Debian Image 2014-05-14
Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
Last login: Thu May 15 02:19:40 2014 from 192.168.7.1
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
domain localdomain
search localdomain
nameserver 192.168.1.1
domain localdomain
search localdomain
nameserver 8.8.8.8
ping: unknown host http://www.google.com

[Raj Bharath RB]

Hi Gary,

Thanks for the detailed explanation.

Post by Gary McKinney
It appears you have done everything right but any little item missed will
stop the link from working properly.
There are several questions you need to ask yourself...
Except where stated otherwise all the tests below are performed from the
BeagleBone system.
1. Does ifconfig command show the correct information for the usb0
interface?

ifconfig command shows as below and I think its fine.

usb0 Link encap:Ethernet HWaddr 32:c8:da:35:6b:a9
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::30c8:daff:fe35:6ba9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:564 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:161443 (157.6 KiB) TX bytes:17438 (17.0 KiB)

Post by Gary McKinney
2. Can you ping the ip address assigned to the usb0 interface
(192.168.7.2)?
If not then there is something not configured properly on your usb0
interface. Check the /etc/network/interfaces file to make sure the entry
for usb0 is correct.

Yes, it pings with 192.168.7.2 ( pings in SSH of putty)

Post by Gary McKinney
3. Can you ping the ip address of the PC's link interface (192.168.7.1)?
If you can not ping the PC link interface address then there is
something incorrectly configured on that interface - double check the
interface settings to make sure the assigned IP address & netmask address
is set correctly.

Yes, I am able to ping 192.168.7.1 also after I added the gateway (
pings in SSH of putty)

Post by Gary McKinney
4. From the PC can you ping the link interface (192.168.7.1)?
If not there is something wrong with the link interface configuration.

Yes, I can. ( in Cmd line of windows 7)

Post by Gary McKinney
5. From the PC can you ping the BeagleBone usb0 interface (192.168.7.2)?
If not double-check the usb0 interface config

Yes, I can. ( in Cmd line of windows 7)

Post by Gary McKinney
6. Can you ping the PC's network bridged IP address (the interface you
have bridged over to the usb link interface on the PC)?
If not make sure you have the bridging setup properly on the PC
interfaces.

I am actually using wifi in my lap (no ethernet cable) and I have shared
this internet with the BBB's USB ethernet. When I typed ipconfig in cmd
line of Windows 7, I got IPv4 Address as 192.168.1.36 in Wireless LAN
adapter. And I was able to ping 192.168.1.36 in my cmd line of Windows 7. I
hope this is what you meant. Please correct me if I am wrong.

Post by Gary McKinney
7. Can you ping the PC's default gateway IP address?

I was able to ping the Default Gateway (192.168.1.254) for this
Wireless LAN adapter in cmd line of Windows 7. But I am not able to
ping 192.168.1.36 and 192.168.1.254 from BBB's SSH

Post by Gary McKinney
If everything is reachable (pingable) up to this point then it has to be
something in the resolver settings (DNS).
Double check to make sure the /etc/resolv.conf file has the proper DNS
server entry so you can resolve FQDN names (those listed in DNS that is).
It has been my experience when network issues crop up they tend to be
something simple but over looked if things had previously worked before
something was changed.

My current settings in /etc/resolv.conf is as below. Is this fine?

domain localdomain
search localdomain
nameserver 192.168.1.1
nameserver 8.8.8.8

Moreover for my Wireless LAN settings, I have selected 'Obtain DNS server
adress automatically' for IPv4 protocol. But for LAN 3 (which is BBB'USB
ethernet), I could only select 'Use the following DNS server address' which
is actually blank.

And also, in Network connections, LAN 3 shows that it has 'No internet
access' and Wireless LAN shows it has internet access.

Please let me know if I there is any issue with DNS server entries and to
change it

Thank you very much for your detailed explanation.

[Raj Bharath RB]

Still not working!!

Post by Raj Bharath RB
Hi Gary,
Thanks for the detailed explanation.

Post by Gary McKinney
It appears you have done everything right but any little item missed will
stop the link from working properly.
There are several questions you need to ask yourself...
Except where stated otherwise all the tests below are performed from the
BeagleBone system.
1. Does ifconfig command show the correct information for the usb0
interface?

ifconfig command shows as below and I think its fine.
usb0 Link encap:Ethernet HWaddr 32:c8:da:35:6b:a9
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::30c8:daff:fe35:6ba9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:564 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:161443 (157.6 KiB) TX bytes:17438 (17.0 KiB)

Post by Gary McKinney
2. Can you ping the ip address assigned to the usb0 interface
(192.168.7.2)?
If not then there is something not configured properly on your usb0
interface. Check the /etc/network/interfaces file to make sure the entry
for usb0 is correct.

Yes, it pings with 192.168.7.2 ( pings in SSH of putty)

Post by Gary McKinney
3. Can you ping the ip address of the PC's link interface (192.168.7.1)?
If you can not ping the PC link interface address then there is
something incorrectly configured on that interface - double check the
interface settings to make sure the assigned IP address & netmask address
is set correctly.

Yes, I am able to ping 192.168.7.1 also after I added the gateway
( pings in SSH of putty)

Post by Gary McKinney
4. From the PC can you ping the link interface (192.168.7.1)?
If not there is something wrong with the link interface configuration.

Yes, I can. ( in Cmd line of windows 7)

Post by Gary McKinney
5. From the PC can you ping the BeagleBone usb0 interface (192.168.7.2)?
If not double-check the usb0 interface config

Yes, I can. ( in Cmd line of windows 7)

Post by Gary McKinney
6. Can you ping the PC's network bridged IP address (the interface you
have bridged over to the usb link interface on the PC)?
If not make sure you have the bridging setup properly on the PC
interfaces.

I am actually using wifi in my lap (no ethernet cable) and I have shared
this internet with the BBB's USB ethernet. When I typed ipconfig in cmd
line of Windows 7, I got IPv4 Address as 192.168.1.36 in Wireless LAN
adapter. And I was able to ping 192.168.1.36 in my cmd line of Windows 7. I
hope this is what you meant. Please correct me if I am wrong.

Post by Gary McKinney
7. Can you ping the PC's default gateway IP address?

I was able to ping the Default Gateway (192.168.1.254) for this
Wireless LAN adapter in cmd line of Windows 7. But I am not able to
ping 192.168.1.36 and 192.168.1.254 from BBB's SSH

Post by Gary McKinney
If everything is reachable (pingable) up to this point then it has to be
something in the resolver settings (DNS).
Double check to make sure the /etc/resolv.conf file has the proper DNS
server entry so you can resolve FQDN names (those listed in DNS that is).
It has been my experience when network issues crop up they tend to be
something simple but over looked if things had previously worked before
something was changed.

My current settings in /etc/resolv.conf is as below. Is this fine?
domain localdomain
search localdomain
nameserver 192.168.1.1
nameserver 8.8.8.8
Moreover for my Wireless LAN settings, I have selected 'Obtain DNS server
adress automatically' for IPv4 protocol. But for LAN 3 (which is BBB'USB
ethernet), I could only select 'Use the following DNS server address' which
is actually blank.
And also, in Network connections, LAN 3 shows that it has 'No internet
access' and Wireless LAN shows it has internet access.
Please let me know if I there is any issue with DNS server entries and to
change it
Thank you very much for your detailed explanation.