Hello,
I'm new to BB and Angstrom. I have connected all the wires correctly
and gotten to the login screen. When I try to ping a website it comes
back with the following message:
ping: bad address 'google.com'
I have been running around in circles on the internet trying to solve
this issue with no avail. Can someone please provide me with detailed
instructions on fixing my problem. Thanks so much!!!
-V
First ping one IP address (next gateway per example) not site like google.com and check network configuration Gateway, NetMask, DNS, etc…
Tanks Armando.
2010/6/15 V <mulaystandard@comcast.net>
Hi V,
Maybe this will help you http://linuxtogo.org/gowiki/AngstromManual#Communications.26Networking.
Will
You need to make sure you have the interface up (use ifconfig) and
configured with the correct IP address.
If you are using usb0 over the OTG interface, the host USB computer
must also have its end of the CDC ethernet configured.
You can try this link for more info (not the NFS stuff though) about
USB OTG interfaces
http://elinux.org/Mount_BeagleBoard_Root_Filesystem_over_NFS_via_USB
Using ifconfig I have found that "eth0" doesn't show up, and according
to a number of sources I think it is needed for internet connection to
work properly. Can someone confirm this? I hope this helps someone
know what should be done for me to get internet.
-V
After noticing that my eth0 connection didn't show up on my ifconfig,
I decided to try some more commands and got the following results:
~# ifconfig eth0
ifconfig: eth0: error fetching interface information: Device not found
~# ifup eth0
ifup: interface eth0 already configured
Another round of searching through the web about this problem led me
to <http://www.mail-archive.com/angstrom-distro-users@linuxtogo.org/
msg02713.html> and the problem seems to be the same, although I am not
using a zippy board. Will the solution still work? I don't want to
cause more problems.
-V
Have you followed the instructions in the Angstrom manual?
http://www.linuxtogo.org/gowiki/AngstromManual#Communications.26Networking
Here's what I did:
* Connect USB OTG port to host PC via USB cable (this provides power
and ethernet).
* Wait for boot
* Loaded g_ether module
* ifconfig usb0
* ip route add default via <PC address>
On PC:
* Watch usb0 come up in /var/log/messages
* ifconfig usb0
* Enabled IP forwarding
* Setup IP masquerade on the PC
Okay, I have realized that I had USB problems earlier due to using a
Rev C3 board and now have seemed to have fixed them. I'm now using the
OTG port as my host port for USB using a USB to USB connector. The BB
detects the eth0 connection and pinging seems to work, but the
internet is still not working.
Here are a few commands and their results:
root@beagleboard:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:D1:1B:45:38
inet addr:10.21.5.184 Bcast:10.21.5.255 Mask:255.255.255.0
inet6 addr: fe80::214:d1ff:fe1b:4538/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3499 errors:0 dropped:0 overruns:0 frame:0
TX packets:616 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:406784 (397.2 KiB) TX bytes:68010 (66.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)
root@beagleboard:~# ifconfig usb0
usb0 Link encap:Ethernet HWaddr EA:D0:33:BC:7C:16
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
root@beagleboard:~# ping google.com
PING google.com (72.14.204.147): 56 data bytes
64 bytes from 72.14.204.147: seq=0 ttl=53 time=562.256 ms
64 bytes from 72.14.204.147: seq=1 ttl=53 time=191.772 ms
64 bytes from 72.14.204.147: seq=2 ttl=53 time=36.285 ms
64 bytes from 72.14.204.147: seq=3 ttl=53 time=35.797 ms
64 bytes from 72.14.204.147: seq=4 ttl=53 time=36.377 ms
--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 35.797/172.497/562.256 ms
root@beagleboard:~# wget google.com
--2010-03-19 14:30:02-- http://google.com/
Resolving google.com... 72.14.204.147, 72.14.204.99,
72.14.204.104, ...
Connecting to google.com|72.14.204.147|:80... connected.
HTTP request sent, awaiting response...
The last command stays in the "awaiting response..." stage until a
(Ctrl+C) is needed to get the prompt back up. Does someone know a
solution to get my internet working? Thanks so much!
-V
Since google.com is resolving to an IP address, it looks like you actually are connected. What are the results from “ping google.com”?
Jeff,
I have tried that command and have listed my results in my previous
post. Ping seems to be working fine.
-V
Yes, I see it now. That shows that you are connected to the Internet and DNS is working.
However, the result from “ifconfig usb0” does not show an ethernet address. It should have a line like “inet addr:ww.xx.yy.zz Bcast:…”
I am just now writing up the process for setting up a tunnel via USB from an Ubuntu host, so I am very curious about getting this to work as well! 
Out of curiosity, can you wget any other pages besides the google home page? How about “wget http://beagleboard.org”?
Hi Jeff,
I have typed some more commands with interesting results. This time I
tried different websites using wget, nslookup, and traceroute. It
seems like on some websites nslookup seems to work and some
(www.cnn.com) it doesn't, and traceroute doesn't seem to get past the
first step. All of this leads me to guess that there is a problem with
the DNS, I'm not sure if this is correct.
I have the commands and results below:
root@beagleboard:~# wget google.com
--2010-03-18 16:18:22-- http://google.com/
Resolving google.com... 72.14.204.103, 72.14.204.104,
72.14.204.99, ...
Connecting to google.com|72.14.204.103|:80... connected.
HTTP request sent, awaiting response...
root@beagleboard:~# wget www.comcast.net
--2010-03-18 16:18:56-- http://www.comcast.net/
Resolving www.comcast.net... 65.199.63.74, 65.199.63.40
Connecting to www.comcast.net|65.199.63.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'
[ <=> ] 74,600 --.-K/s
[ <=> ] 74,600 --.-K/
s
root@beagleboard:~# wget www.cnn.com
--2010-03-18 16:20:32-- http://www.cnn.com/
Resolving www.cnn.com... failed: Name or service not known.
Resolving www.cnn.com... failed: Name or service not known.
root@beagleboard:~# nslookup google.com
Server: 10.21.5.1
Address 1: 10.21.5.1
Name: google.com
Address 1: 72.14.204.103 iad04s01-in-f103.1e100.net
Address 2: 72.14.204.104 iad04s01-in-f104.1e100.net
Address 3: 72.14.204.99 iad04s01-in-f99.1e100.net
Address 4: 72.14.204.147 iad04s01-in-f147.1e100.net
root@beagleboard:~# nslookup www.cnn.com
Server: 10.21.5.1
Address 1: 10.21.5.1
nslookup: can't resolve 'www.cnn.com'
root@beagleboard:~# nslookup www.comcast.net
Server: 10.21.5.1
Address 1: 10.21.5.1
Name: www.comcast.net
Address 1: 65.199.63.74
Address 2: 65.199.63.40
root@beagleboard:~# traceroute google.com
traceroute: warning: google.com has multiple addresses; using
72.14.204.103
traceroute to google.com (72.14.204.103), 30 hops max, 38 byte packets
1 10.21.5.1 (10.21.5.1) 1.618 ms 2.808 ms 0.854 ms
2 * * *
3 * * *
root@beagleboard:~# traceroute www.cnn.com
traceroute: www.cnn.com: Host name lookup failure
root@beagleboard:~# traceroute www.comcast.net
traceroute: warning: www.comcast.net has multiple addresses; using
65.199.63.74
traceroute to a1526.g.akamai.net (65.199.63.74), 30 hops max, 38 byte
packets
1 10.21.5.1 (10.21.5.1) 1.312 ms 1.251 ms 0.732 ms
2 * * *
Once again I required a cancel (Ctrl + c) to get out of wget and
traceroute. I hope this might provide further insight to what my
problem is. If someone has a solution please post it, thanks!!!
-V
Have you changed /etc/resolv.conf?
/etc/resolv.conf needs to contain nameserver entries that are local to
you otherwise the system could be doing DNS lookups across the globe.
Hi Richard,
I have modified it, but it appears that it is recreated on startup by
NetworkManager to a default configuration. I have also added some
websites and ip addresses on the /etc/hosts file, and wget seems to
work on those but load bar always stops at around 98-99% and gets
stuck there. At this point I'm completely baffled by this problem and
I've had it for 3-4 days. If anyone has any idea on what to check or
modify next, please post it.
-V
The only thing I can think of that changes resolv.conf is a DHCP
client. Are you running one? If you are the server needs to provide
sensible DNS settings.
Is there any NetworkManager or similar daemons running that might
interfere with network config.
If you manually change resolv.conf, do you get better performance
while it is changed?
The stopping at 99% is baffling. The network cannot know how big the
file is. Try different files and servers.
Can you run a web/file server on your dev PC and transfer from that OK?
Might also be worth turning off TCP window scaling as this can break
data transfers when they begin to ramp up. There could be some old
gateway in the path that does not understand window scaling.
Run tcpdump/wireshark on the PC. This will shed light on what is happening.