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...
On Saturday, January 17, 2015 at 6:47:24 AM UTC-5, 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].
For more options, visit https://groups.google.com/d/optout.
