I'm running Windows XP and am able to talk to the BeagleBone through
both the USB and Ethernet connections to the board. I'm doing a
shared wireless internet connection for the BB through Windows. This
works well enough that ifconfig will show me an IP address for eth0.
However, when I try to do an opkg update, it is unable to reach the
feed. Trying to ping an external IP from the BB also fails to connect
to anything. On the windows side, the shared connection has DHCP
(67), DHCP(68), DNS, FTP, HTTPS, Telnet, UPnP (TCP), UPnP (UDP), and
HTTP services shared. What am I missing? I'm guessing the problem is
some service is not making it all the way through the wireless
connection. Any suggestions?
John
Gerald,
Thanks for the pointer. Unfortunately, I don't believe that anything
on this page applies. A bit more detail. My board is Rev A3. It is
able to obtain a lease, hence my ability to see what IP is assigned to
eth0 when I do an ifconfig on the BB. I can also use PuTTY to connect
with an SSH session to the BB over Ethernet as well as make a serial
connect over USB. I have 3 different microSD cards with different
versions of the image. This problem seems to be true regardless of
image. I find myself stymied since I can't update or upgrade the
packages as necessary.
John
OK, so now that you have told me the revision, it does help.
I agree this is clearly a SW update issue. I will need to defer to some others on the list to help you out.
Gerald
Are you getting a DNS address in your configuration? you may need to configure it depending on how your DHCP is set up. You can do that in /etc/resolv.conf.
I had this same issue until I set up DHCP… But I was forced to do a hard reboot for it to take effect for some reason… Have you tried that? Maybe do that one first?
Charlie,
Thanks for the suggestion. I'm new enough to this level of Linux that
I'm not sure I've done this correctly, but here is what I've done:
echo 'nameserver 8.8.8.8' >> resolv.conf
route add default gw 192.168.7.1
root@beaglebone:/etc# cat resolv.conf
# Generated by Connection Manager
nameserver 127.0.0.1
nameserver 8.8.8.8
root@beaglebone:/etc# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
default Gladius.local 0.0.0.0 UG 0 0
0 usb0
default Gladius.mshome. 0.0.0.0 UG 0 0
0 eth0
192.168.0.0 * 255.255.255.0 U 0 0
0 eth0
192.168.0.1 * 255.255.255.255 UH 0 0
0 eth0
192.168.7.0 * 255.255.255.252 U 0 0
0 usb0
Unfortunately, this didn't seem to make any difference. Perhaps I'm
doing this wrong. Any suggestions? Thanks.
John
Ok.. I went back and reviewed everything here.. but I'm a little confused... are you trying to do this from eth0 or the USB via Windows?
I would suggest connecting only through the eth0 via Putty or something like that and have the USB disconnected. If you are trying to do both, the BB may be trying to go via Windows and may be hitting a Firewall issue there or something... Taking out Windows from the equation keeps it simpler.
Charlie,
I have USB connected to get the eth0 ip address using ifconfig. I
then disconnect the USB wire. I connect to the BB with PuTTY using
the eth0 ip address. I do notice that the 192.168.7.x sites are
completely unavailable when I only have Ethernet connected. The eth0
ip is one that was dynamically assigned. This makes no difference in
trying to ping an external site. I've also tried this with just the
USB connected. Nothing seems to work in trying to reach an external
address. Any other suggestions?
John
Try changing your default Gateway from 192.168.7.1 to 192.16.0.1 From what it sounds like you originally set it up with the Ethernet over USB. (the 7.0 network).. But since you set 7.1 (your local PC) as your default gateway and then disconnect the USB, you are no longer able to reach your default gateway so it's dropping the packets.
192.168.0.1 "should" be your home network's router and not your PC.
Charlie,
The route command shows:
root@beaglebone:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
default Gladius.mshome. 0.0.0.0 UG 0 0
0 eth0
192.168.0.0 * 255.255.255.0 U 0 0
0 eth0
192.168.0.1 * 255.255.255.255 UH 0 0
0 eth0
root@beaglebone:~#
I take this to mean the default gateway is 192.168.0.1. When I try to
ping this address, I get no response. The BB can ping itself. The
eth0 address is 192.168.0.59. Pinging this address works fine. In
case you really meant set the gateway to 192.16.0.1, route tells me
this network is unreachable. I know the board must have some
connection since it does get its eth0 ip address over the network.
I'm just not sure what to try next to mae a connection from the BB to
the network so I can do an opkg update. Any other thoughts? Thanks.
John
The only other thing I can think of is to change "Gladius.mshome." to the actual IP address (assuming of course that Gladius is your Router/Firewall and not your PC)...
if you feel comfortable can you post both your /etc/resolv.conf and your /etc/sysconfig/network-scripts/ifcfg-eth0 ?? They should be rather small in length.
Charlie,
Sorry to be so long in responding, I've been under the weather.
Gladius is the name of the PC. There is no network-scripts directory
or any file starting with ifcfg*. The resolv.conf file shows:
# Generated by Connection Manager
nameserver 127.0.0.1
nameserver 8.8.8.8
route shows:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
default Gladius.mshome. 0.0.0.0 UG 0 0
0 eth0
192.168.0.0 * 255.255.255.0 U 0 0
0 eth0
192.168.0.1 * 255.255.255.255 UH 0 0
0 eth0
192.168.7.0 * 255.255.255.252 U 0 0
0 usb0
ifconfig shows:
eth0 Link encap:Ethernet HWaddr D4:94:A1:37:71:11
inet addr:192.168.0.153 Bcast:192.168.0.255 Mask:
255.255.255.0
inet6 addr: fe80::d694:a1ff:fe37:7111/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:276 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:57307 (55.9 KiB) TX bytes:8975 (8.7 KiB)
Interrupt:40
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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:689 (689.0 B) TX bytes:689 (689.0 B)
usb0 Link encap:Ethernet HWaddr 32:06:4B:C4:C2:B0
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:
255.255.255.252
inet6 addr: fe80::3006:4bff:fec4:c2b0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:138 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16512 (16.1 KiB) TX bytes:7542 (7.3 KiB)
Not quite sure what to do next.
John