Posts made by victoriano

@crispyoz it is also possible to re-enable it permanently only for your user in the Ubuntu system and your Onion, by editing or creating a file named "config" inside your ~/.ssh directory with something like:

Host onion
    HostKeyAlgorithms+=ssh-rsa

onion here is your Onion IP address or the name you use to ssh into it.
I use it a lot to be able to access old systems without having to type the options once and again.
It is also useful for reenabling KeyAlgorithms or setting per host options or user name, or ...
Use it with care and only when needed for a given host

Posting the output of "ip a", "ip r" and, very specially, "brctl show" would be very useful to help diagnose the situation and see if you have a router or a bridge.

Why don't you just read the (pseudo) file? No need to open new processes. Using

w = int(open('/sys/class/leds/omega2lte:blue:wifi/brightness').read())

Will give you what you need from python in a pythonic way.

I always prefer mainline distros over very specialised ones. Do you know if OpenWRT 19.07 supports Omega2 Dash features?

@crispyoz fully agreed. But you can then use the neighbour table (a.k.a. ARP in IPv4 world) to see if those you have found via grep have shown any vital signs recently. Of course, if your Omega is their router, they SHOULD (RFC 2119) show in that table if they have a minimum activity.

if you do

logread | grep dhcp

you will see the associated stations getting ip addresses assigned to their MAC addresses, like:

Wed Sep 30 16:57:05 2020 daemon.info dnsmasq-dhcp[1877]: DHCPDISCOVER(br-wlan) 84:cf:bf:xx:xx:xx
Wed Sep 30 16:57:05 2020 daemon.info dnsmasq-dhcp[1877]: DHCPOFFER(br-wlan) 192.168.3.173 84:cf:bf:xx:xx:xx
Wed Sep 30 16:57:05 2020 daemon.info dnsmasq-dhcp[1877]: DHCPDISCOVER(br-wlan) 84:cf:bf:xx:xx:xx
Wed Sep 30 16:57:05 2020 daemon.info dnsmasq-dhcp[1877]: DHCPOFFER(br-wlan) 192.168.3.173 84:cf:bf:xx:xx:xx
Wed Sep 30 16:57:05 2020 daemon.info dnsmasq-dhcp[1877]: DHCPREQUEST(br-wlan) 192.168.3.173 84:cf:bf:xx:xx:xx
Wed Sep 30 16:57:05 2020 daemon.info dnsmasq-dhcp[1877]: DHCPACK(br-wlan) 192.168.3.173 84:cf:bf:xx:xx:xx

if you are not using DHCP because you use fixed addresses or IPv6, then

ip neigh show dev br-wlan

will show know MAC addresses, like:

192.168.3.173 lladdr 84:cf:bf:xx:xx:xx ref 1 used 0/0/0 probes 1 REACHABLE
fe80::6:af0a:307c:37ae lladdr 84:cf:bf:xx:xx:xx used 0/0/0 probes 1 REACHABLE

I'd recommend using the new iw command but, although it exists in our Omegas, the modern nl80211 seems not to be available, so it does not work. If it did, it would be very easy to dump the connected stations.

Friends, have you noticed the message in the first posted image warning about a CRC problem and use of default environment?

I'm attaching the image with a red arrow pointing to the message. Maybe that's the root cause of all problems in this thread...

@Nathan-Guyette if the code is similar and it just some parameter change (as your beeping examples), I'd use a configuration file that is retrieved at startup using http(s) either by the program or the system (wget) and then sets the running parameters accordingly.
Selecting the appropriate configuration on the web server can be done based on the requesting machine IP or sending some parameter.
If you want a complete change of behaviour, the you can use wget to retrieve the whole program and run it.
/etc/rc.local is your friend

@crispyoz just to increase the number of googled terms ... my spider was implemented on OpenVMS

@crispyoz I lov lynx I even used it to create a web spider when Google inventors were in high school

@Ralph-Hulslander this would not work. The kind of browser you are thinking about requires an amount of supporting "material" that will not even fit in the Dash. What's the problem you want to solve. Maybe a browser is not the best solution.

Hi, I've been searching the forum but none of the posts I've found apply.

I have a device (SIM808) that's controlled via two serial ports. I've successfully connected it to the Omega Dash through pins 45 and 46, but none of the pins I've seen referenced on other posts is available on the connector.

I suspect that the Dash's screen needs quite a bunch of the GPIOs and the ones needed for /dev/ttyS0 are used for something. Is this true?

Thanks.