I suggest that you not use the USB connection to the BBB, but instead hardwire it directly to your Ethernet network.
The USB link works for simple applications, but some combination of the BBB widget and Windows USB to Ethernet bridging behavior can get in the way of more sophisticated applications. Set it up like a more traditional network element. --- Graham == On Thursday, August 11, 2016 at 11:58:58 AM UTC-5, Lidia Toscano wrote: > > I am using Debian GNU/Linux 8 beaglebone ttyGS0 > > BeagleBoard.org Debian Image 2016-06-19 > > Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > > default username:password is [debian:temppwd] > > The IP Address for usb0 is: 192.168.7.2 > > The IP Address for usb0 is: 192.168.7.2 > > > I am not sure how, I was doing some updates using apt-get update this > weekend and downloading some software on the BBB and now I cannot bring the > Ethernet back up. I lost the configuration in the ifconfig file. I went > from this: > > Last login: Sun Jun 19 18:17:47 2016 > root@beaglebone:~# ifconfig > eth0 Link encap:Ethernet HWaddr 54:4a:16:df:9a:7a > inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::564a:16ff:fedf:9a7a/64 Scope:Link > UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1 > RX packets:1469 errors:0 dropped:0 overruns:0 frame:0 > TX packets:462 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:143743 (140.3 KiB) TX bytes:166998 (163.0 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:36976 errors:0 dropped:0 overruns:0 frame:0 > TX packets:36976 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1 > RX bytes:2847688 (2.7 MiB) TX bytes:2847688 (2.7 MiB) > > usb0 Link encap:Ethernet HWaddr 54:4a:16:df:9a:70 > inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252 > inet6 addr: fe80::564a:16ff:fedf:9a70/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3921 errors:0 dropped:7 overruns:0 frame:0 > TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:327206 (319.5 KiB) TX bytes:7382 (7.2 KiB) > > root@beaglebone:~# > > *************************** > to this > *************************** > root@beaglebone:~# ifconfig > eth0 Link encap:Ethernet HWaddr 54:4a:16:df:9a:7a > UP BROADCAST MULTICAST DYNAMIC 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) > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > as you can see, I've lost the inet addr in eth0 and I don't have a usb0 at > the end. The interesting thing is that I can get the Ethernet access at > home with my router. I think all of this changed when I did an upt-get > update while installing dronekit. > > The /etc/network/interfaces file seems to be ok: > > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > auto eth0 > iface eth0 inet static > address 192.168.1.12 > netmask 255.255.255.0 > gateway 192.168.1.1 > > > # Example to keep MAC address between reboots > #hwaddress ether DE:AD:BE:EF:CA:FE > > # The secondary network interface > #auto eth1 > #iface eth1 inet dhcp > > # WiFi use: -> connmanctl > > # 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.252 > > > > Does anyone have any idea what happened and what I can do to fix it? > > Thank you very much. > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/698da8d7-0ec5-4c21-877c-780bef567879%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
