On Mon, 8 Jun 2020 15:00:36 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user
me-OZSSi2IBlpFBDLzU/[email protected] wrote:
>In regards to connections I've tried the following:
>
> - Micro USB from BBB to Host PC (two different cables)
> - Micro USB to phone charger (USB-A / 15W) and then over wifi only
> - Micro USB from Official Raspberry Pi Charger (5V 2.5A) and then over
> wifi only
>
>It seems, when you connect the USB, it creates an ethernet over usb
>connection, so this has been the most logical thign to use to try and issue
>commands via SSH, although as above, I've tried doing it only via WiFi as
>well and same issue.
>
Unless the host "PC" has been configured to do (what Windows calls)
Internet Connection Sharing (Linux/Mac may have different names for setting
up the gateway/routing) that USB link is ONLY between the Beagle and the
Host; attempt to connect through the host to the internet will fail
USB-only:
-=-=-=-
debian@beaglebone:~$ ping 192.168.7.1
PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
64 bytes from 192.168.7.1: icmp_seq=1 ttl=128 time=0.421 ms
64 bytes from 192.168.7.1: icmp_seq=2 ttl=128 time=0.489 ms
64 bytes from 192.168.7.1: icmp_seq=3 ttl=128 time=0.514 ms
64 bytes from 192.168.7.1: icmp_seq=4 ttl=128 time=0.469 ms
64 bytes from 192.168.7.1: icmp_seq=5 ttl=128 time=0.469 ms
^C
--- 192.168.7.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 11ms
rtt min/avg/max/mdev = 0.421/0.472/0.514/0.036 ms
debian@beaglebone:~$ ping 8.8.8.8
connect: Network is unreachable
debian@beaglebone:~$ sudo apt install inetutils-traceroute
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
inetutils-traceroute
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 202 kB of archives.
After this operation, 242 kB of additional disk space will be used.
Err:1 http://deb.debian.org/debian buster/main armhf inetutils-traceroute
armhf 2:1.9.4-7
Temporary failure resolving 'deb.debian.org'
E: Failed to fetch
http://deb.debian.org/debian/pool/main/i/inetutils/inetutils-traceroute_1.9.4-7_armhf.deb
Temporary failure resolving 'deb.debian.org'
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?
debian@beaglebone:~$
-=-=-=-
I don't have Blue, my Black has wired Ethernet... Reconnecting the
cable...
-=-=-=-
debian@beaglebone:~$ ping 192.168.7.1
PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
64 bytes from 192.168.7.1: icmp_seq=1 ttl=128 time=0.455 ms
64 bytes from 192.168.7.1: icmp_seq=2 ttl=128 time=0.508 ms
64 bytes from 192.168.7.1: icmp_seq=3 ttl=128 time=0.449 ms
64 bytes from 192.168.7.1: icmp_seq=4 ttl=128 time=0.469 ms
^C
--- 192.168.7.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 6ms
rtt min/avg/max/mdev = 0.449/0.470/0.508/0.027 ms
debian@beaglebone:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=27.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=27.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=27.5 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=27.3 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 18268ms
rtt min/avg/max/mdev = 27.323/27.520/27.686/0.211 ms
debian@beaglebone:~$ sudo apt install inetutils-traceroute
[sudo] password for debian:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
inetutils-traceroute
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 202 kB of archives.
After this operation, 242 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main armhf inetutils-traceroute
armhf 2:1.9.4-7 [202 kB]
Fetched 202 kB in 1s (290 kB/s)
Selecting previously unselected package inetutils-traceroute.
(Reading database ... 85321 files and directories currently installed.)
Preparing to unpack .../inetutils-traceroute_2%3a1.9.4-7_armhf.deb ...
Unpacking inetutils-traceroute (2:1.9.4-7) ...
Setting up inetutils-traceroute (2:1.9.4-7) ...
update-alternatives: using /usr/bin/inetutils-traceroute to provide
/usr/bin/traceroute (traceroute) in auto mode
Processing triggers for man-db (2.8.5-2) ...
debian@beaglebone:~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max
1 192.168.1.254 0.644ms 0.720ms 0.579ms
2 76.255.152.1 18.076ms 16.453ms 36.656ms
3 71.152.176.29 17.860ms 18.088ms 18.039ms
4 12.123.7.142 33.088ms 30.803ms 31.560ms
5 12.122.133.45 28.229ms 26.917ms 26.958ms
6 12.255.10.56 27.793ms 27.037ms 26.658ms
7 * * *
8 8.8.8.8 27.656ms 26.819ms 27.218ms
debian@beaglebone:~$
-=-=-=-
> - Stock pre-installed (ie. from factory, dated 2017 from memory)
> - AM3358 Debian 10.3 2020-04-06 4GB SD IoT
>
> <https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz>
> - AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher
I typically avoid the flasher images... I prefer to make sure the image
works on SD card first -- and then edit the /boot/uEnv.txt file to convert
the image into a flasher.
>
>Always the same result - reverting to read-only when doing writes with WiFi
>on - except when I tried to modify the kernel parameters as previous post
>with the vm.min_free_kbytes paramter - which did seem to work for a long
>time - but after doing an apt update/upgrade it soon reverted to read-only
>as well, which was disappointing.
>
Have you tried monitoring memory usage in real-time? "top" command?
Check
MiB Mem : 483.4 total, 237.9 free, 58.4 used, 187.2 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 416.8 avail Mem
free, avail, and buff/cache values while performing one of these operations
that are "hanging". Remember that Beaglebone Black/Blue/etc. tend to only
have 512MB of RAM, and run with NO swap file. If avail and buff/cache start
falling drastically (and free is minimal) you may need to try setting up a
(slow, and SD card deadly) swap file (I'm presuming you aren't going to
connect/format a USB hard drive for this).
I have trouble visualizing the WiFi traffic overrunning -- a WiFi stack
should, I'd think, drop the inbound packet if there is no buffer space for
it, expecting (TCP) higher levels to re-request the packet when found
missing, or (UDP) it will be repeated on its own IF a periodic sending (UDP
ensures that one either receives the complete packet or none in a read; TCP
ensures that one will receive the packet but it may dribble in small
chunks, multiple separate sends may be combined, etc.)
Same data from an R-Pi 3B+
MiB Mem : 926.1 total, 346.7 free, 158.4 used, 421.0 buff/cache
MiB Swap: 100.0 total, 100.0 free, 0.0 used. 702.8 avail Mem
{I had an apt upgrade running in another window -- that and having the
X-window system running likely explains the 100MB additional usage}
I note that it is reporting a 100MB swap -- though I don't know where
it was configured. It isn't in fstab.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/a1etdf1oqjnucs3jabogfv87cvrtncsqj4%404ax.com.
