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.
[image: Inline image 1]
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 . . .
On Thu, Aug 11, 2016 at 5:41 PM, William Hermans <[email protected]> wrote:
> Ok, so it seems as though perhaps your Win10 machine has reverted back to
> dhcp. Can you check that for us ?
>
> On Thu, Aug 11, 2016 at 2:31 PM, Lidia Toscano <[email protected]>
> wrote:
>
>> 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
>>
>>
>> On Thu, Aug 11, 2016 at 5:29 PM, Lidia Toscano <[email protected]>
>> wrote:
>>
>>> # 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
>>>
>>>
>>> On Thu, Aug 11, 2016 at 3:48 PM, William Hermans <[email protected]>
>>> wrote:
>>>
>>>> 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
>>>>
>>>>
>>>> On Thu, Aug 11, 2016 at 12:42 PM, William Hermans <[email protected]>
>>>> wrote:
>>>>
>>>>> 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 ?
>>>>>
>>>>> On Thu, Aug 11, 2016 at 9:58 AM, Lidia Toscano <
>>>>> [email protected]> 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/c7f4ec1a-d11b-
>>>>>> 407b-aae1-5813a36a07f8%40googlegroups.com
>>>>>> <https://groups.google.com/d/msgid/beagleboard/c7f4ec1a-d11b-407b-aae1-5813a36a07f8%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>>
>>>> --
>>>> For more options, visit http://beagleboard.org/discuss
>>>> ---
>>>> 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/to
>>>> pic/beagleboard/1oGhI7NY1t0/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> [email protected].
>>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>>> gid/beagleboard/CALHSORrucdpqNzmDL07tDFUE86s4LQ4TR_J15OwBVOB
>>>> aJi9WUw%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/beagleboard/CALHSORrucdpqNzmDL07tDFUE86s4LQ4TR_J15OwBVOBaJi9WUw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>> --
>> 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/ms
>> gid/beagleboard/CALseTBWTa2wkThGu46yZg%3D9KkgPRDwQ_
>> B76ieeiSg%3DNAhNXXXQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CALseTBWTa2wkThGu46yZg%3D9KkgPRDwQ_B76ieeiSg%3DNAhNXXXQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> 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
> [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/CALHSORptUvY9JxMtmHpQsyuF%2BKqhdm5QFBkfwAFb7Qddp5NvAw%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORptUvY9JxMtmHpQsyuF%2BKqhdm5QFBkfwAFb7Qddp5NvAw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
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/CALseTBX7CgJsxCakXdeopUYcELDKSQC3MQWW65_GFrWVwx9ZTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
