On Mon, Mar 21, 2016 at 11:59 AM, Daniel Benevides
<[email protected]> wrote:
> Hello Robert...
>
> Thank you for answering so quickly.
>
> Unfortunately, the problem remains.
>
> Via eth0 I cannot access the BBB from the network nor from it I can reach
> any IP destination on my network.
>
> What I did:
>
> 1) I flashed the BBB again, with the
> BBB-eMMC-flasher-debian-8.3-iot-armhf-2016-03-13-4gb image.
>
> 2) I removed connman (apt-get remove connman).
>
> 3) I updated the interfaces file:
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> allow-hotplug eth0
>
> iface eth0 inet static
>          address 192.168.20.79
>          netmask 255.255.255.0
>          network 192.168.20.0
>          broadcast 192.168.20.255
>          gateway 192.168.20.1
>          dns-name-servers 192.168.20.200
>
> # Ethernet/RNDIS gadget (g_ether)
> # Used by: /opt/scripts/boot/autoconfigure_usb0.sh
> iface usb0 inet static
>     address 192.168.7.2
>     netmask 255.255.255.252nor
>     network 192.168.7.0
>     gateway 192.168.7.1
>
> 4) Turned off the BBB and turned it on.
>
> 5) Tried to connect to the BBB using PuTTY on the IP 192.168.20.79, but with
> no luck.
>
> 6) Also plugged and unplugged the network cable -- with no luck also.
>
> 7) Over serial connection, the BBB shows me this welcome message (using
> PuTTY):
>
> Debian GNU/Linux 8 beaglebone ttyGS0
>
> BeagleBoard.org Debian Image 2016-03-13
>
> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
>
> default username:password is [debian:temppwd]
>
> The IP Address for eth0 is: 192.168.20.79
> The IP Address for usb0 is: 192.168.7.2
> beaglebone login:
>
>
> -- The /etc/resolv.conf file is empty.
>
> -- The ifconfig command returns this:
>
> eth0      Link encap:Ethernet  HWaddr 54:4a:16:f0:f1:f0
>           inet addr:192.168.20.79  Bcast:192.168.20.255  Mask:255.255.255.0
>           inet6 addr: fe80::564a:16ff:fef0:f1f0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1432 errors:0 dropped:3 overruns:0 frame:0
>           TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:163999 (160.1 KiB)  TX bytes:7927 (7.7 KiB)
>           Interrupt:175
>
> 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:65536  Metric:1
>           RX packets:6087 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6087 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:492956 (481.4 KiB)  TX bytes:492956 (481.4 KiB)
>
> usb0      Link encap:Ethernet  HWaddr 54:4a:16:f0:f1:f1
>           inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>           inet6 addr: fe80::564a:16ff:fef0:f1f1/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:799 errors:0 dropped:5 overruns:0 frame:0
>           TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:119293 (116.4 KiB)  TX bytes:9570 (9.3 KiB)
>
>
> -- The route -n command returns this:
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 0.0.0.0         192.168.20.1    0.0.0.0         UG    0      0        0 eth0
> 192.168.7.0     0.0.0.0         255.255.255.252 U     0      0        0 usb0
> 192.168.20.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
>
>
> -- The iptables -L command returns this:
>
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
>
> Do you have any other ideas on how to solve this?

Not really, as i never use static routes.  But what you have now
'should' work...

I guess, are you sure your cable is correct, (aka a cross over)...

Otherwise, I'd just stick the beagle's mac into your dhcp server. ;)

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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.

Reply via email to