Hi Jon - thanks for your input.
This is a snapshot of my working wlan0
wlan0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.1.50 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::8291:33ff:fe4a:4223 prefixlen 64 scopeid 0x20<link>
ether 80:91:33:4a:42:23 txqueuelen 1000 (Ethernet)
RX packets 20004 bytes 4482231 (4.2 MiB)
RX errors 0 dropped 375 overruns 0 frame 0
TX packets 2130 bytes 245657 (239.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I am indeed using connman -- what do those two additional settings do?
Output of `route`:
debian ~ $ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0
wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
wlan0
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0
wlan0
192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0 usb1
192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
192.168.8.0 0.0.0.0 255.255.255.0 U 0 0 0
SoftAp0
Best,
Matt
On Thursday, July 9, 2020 at 5:02:44 PM UTC-7, jonnymo wrote:
>
> I suspect your resolv.conf got set back to the default with no nameservers
> listed when the USB ethernet port went offline.
>
> How do you have your wlan0 configured?
> If you used connman, you can add the following to your connman settings:
> Ex:
>
> * IPv4.gateway=192.168.2.1 Nameservers=8.8.8.8;8.8.4.4;4.4.4.4;*
>
> Typing 'route' should show your which network device the traffic is going
> down.
>
> Also, you can test this by using ping and specifying the ethernet port to
> use:
> Ex:
> *ping -I wlan0 google.com <http://google.com>*
>
> Cheers,
>
> Jon
>
>
> On Thu, Jul 9, 2020 at 4:10 PM Dennis Lee Bieber <dennis...@gmail.com
> <javascript:>> wrote:
>
>> On Thu, 9 Jul 2020 11:55:02 -0700 (PDT), in
>> gmane.comp.hardware.beagleboard.user Manderson
>> <matthew...> wrote:
>>
>> >Hi all,
>> >
>> >I typically take the wired approach when connecting to my Beaglebone
>> (plug
>> >in USB-C power to a port on my laptop and ssh with the 192.168.6.2 IP).
>>
>> What type of computer are you using (OS)? I ask as Windows
>> normally
>> uses 192.168.7.x, Mac the 192.168.6.x, and Linux apparently works with
>> both
>> (they are, I believe, slightly different USB<>Ethernet protocols).
>>
>> >I've noticed, however, in the past several days that my BBAI loses wlan
>> >connectivity if my host computer goes to sleep (e.g. overnight). Pinging
>>
>> Odds are very good that the USB port powers off when the host
>> sleeps.
>> That means the BBAI is getting a very rude power drop -- risking file
>> system corruption, and who knows what may happen when the host wakes up
>> and
>> the BB AI reboots.
>>
>> Also, it may be that you aren't even using the WiFi connection --
>> if
>> the host is performing the equivalent of "Internet Connection Sharing"
>> your
>> ...
>>
>> >google.com after this happens results in
>> >debian ~ $ ping google.com
>> >ping: google.com: Temporary failure in name resolution
>> >debian ~ $ ping 8.8.8.8
>> >connect: Network is unreachable
>>
>> would be trying to go through the USB gadget (though I'd think if that was
>> active before the sleep, it would reactivate after the sleep also).
>>
>> >
>> >2) If my board's wlan is dependent on my computer also being connected
>> to
>> >wifi, then would it be detrimental to power my BBAI off a wall outlet
>> and
>> >USB-C wall charger instead of plugging into my computer? Or would I not
>> >even be able to ssh into it?
>>
>> Nothing in your post confirms that you even had a WiFi connection
>> to
>> some shared router (if you had, you wouldn't be using 192.168.6.x to
>> connect to the BB AI, but instead be using an IP number -- or hostname:
>> beaglebone or beaglebone.local -- to connect using a path through the
>> router. Does your router even show the BBAI as a Wireless client?
>>
>> Even if the USB port remains powered while the host sleeps, if
>> you were
>> going via ICS (BBAI<>USB gadget<>host WiFi [or cable]<>router<>ISP), the
>> host WiFI may go down when the host sleeps, and possibly it gets a
>> different DHCP assignment on wake-up which is not being reflected in
>> routing tables for the USB gadget.
>>
>>
>>
>> --
>> Dennis L Bieber
>>
>> --
>> 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 beagl...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/c58fgfp0p35v399encr2d1v1i6han23eov%404ax.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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/a4631369-a8b5-40f9-aa53-e05a649029f7o%40googlegroups.com.
