Lost ethernet downloading dronekit

[Lidia Toscano]

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.

[William Hermans]

So, I'm *guessing* that connman is responsible here. BUt since I despise connman, and like tools, I do not use it. So . . . I do not know how they work.

@Robert,

connman is running on that image stock ?

--
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 beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c7f4ec1a-d11b-407b-aae1-5813a36a07f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[William Hermans]

Show us your /etc/network/interfaces file - Lidia.

$ cat /etc/network/interfaces

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0

[Lidia Toscano]

# 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

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/1oGhI7NY1t0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrucdpqNzmDL07tDFUE86s4LQ4TR_J15OwBVOBaJi9WUw%40mail.gmail.com.

[Lidia Toscano]

Sorry about that . . . here it is

# 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

    network 192.168.7.0

    gateway 192.168.7.1

[William Hermans]

Ok, so it seems as though perhaps your Win10 machine has reverted back to dhcp. Can you check that for us ?

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALseTBWTa2wkThGu46yZg%3D9KkgPRDwQ_B76ieeiSg%3DNAhNXXXQ%40mail.gmail.com.

[William Hermans]

• Bottom right task bar right click the network icon
• Select Network and sharing center
• top left click Change adapter settings
• Right click your ethernet adapter and select the properties button
  
• Select Internet protocol 4(TCP/IPv4) then click the properteis button just under that

ON that page make sure the Adapter properties are fill out correctly. If it's set to "Obtain an IP address automatically" then it is set to dhcp and it will not work when the beaglebone is connected directly to your latops ethernet port. This would be why your router works at home, but not when you connect directly when away form your home router.

[William Hermans]

Hmm and actually your beaglebones ethernet port is not taking an IP.  Issue . . .

# ifup eth0

From your command line

[Lidia Toscano]

Ok, there are gremlins here . . . I don't know if powering down made a difference but here is a snap shot of the network settings.  I didn't do anything and it magically started working again . . . now my ifconfig is almost back to normal.

except I am still missing the USB0 part.

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:4881 errors:0 dropped:0 overruns:0 frame:0

          TX packets:3226 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:455824 (445.1 KiB)  TX bytes:1007926 (984.3 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:193 errors:0 dropped:0 overruns:0 frame:0

          TX packets:193 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1

          RX bytes:13904 (13.5 KiB)  TX bytes:13904 (13.5 KiB)

Frustrating to not know what fixed it!  It must be time to go home . . .

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORptUvY9JxMtmHpQsyuF%2BKqhdm5QFBkfwAFb7Qddp5NvAw%40mail.gmail.com.

[William Hermans]

So for completeness. The default gateway on the Windows machine is wrong for the network when your beaglebone and laptop are directly connected together.

As far as USB networking I'm not 100% sure is going on there . . . I'd need hands on access to your hardware to figure that out. But it almost seems as though your do not have a USB cable connected. It's been my experience that the USB network gadget driver won't take an IP unless it's connected to the host machine in this case.

On Thu, Aug 11, 2016 at 3:16 PM, William Hermans <yyr...@gmail.com> wrote:

Derek has a decent connman walk through here: http://derekmolloy.ie/set-ip-address-to-be-static-on-the-beaglebone-black/#Using_Connman

But you need to understand what an IP address *is*, and how to setup a network. Which you can find too much information here: https://www.debian.org/doc/manuals/debian-reference/ch05.en.html but that's everything you'd ever need to know. But very brief crash course.

Your network is 192.168.1.* ( commonly represented in Linux as 192.168.1.0 )

Your gateway's IP address  is 192.168.1.1

Your Beaglebone's IP address is 192.168.1.12

Then I'm not sure what your Windows machine is set to IP address wise. I'm assuming your homes router has taken on the role of the gateway, so it's IP address is probably 192.168.1.1.

So here is the "vicious circle". When away form home, and only the Beaglebone is connected to your laptop. There would be no gateway set. . .

*************************************************************

But now I see you've posted again, and the gateway you have set on your windows machine is incorrect for the IP addresses you have set for your laptop, and beaglebone. It is possible that Windows did this on it's own because at home that's the routers network.

So here is what you need to do. You need to find a network wiz local to you, and have that person setup your network up for you so that you can have your beaglebone connected to your laptop away form home, or have them connected directly together so that in both cases you'll still have a valid network setup. This is getting too complicated to fix over the internet. e.g. some one needs to have physical access to your network to see how things are setup, and that is nigh impossible for anyone to do over the internet . . . Then if someone does contact you directly via email because of this post. Do not fall for it and give them access to your home network . .

[Graham]

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

==