@Johan-Adler in some situations power supply can be a problem. Did you use in both tests the same power source? Please verify problem using different power sources (capable of minimum 1A).
You can also try manually scan wireless network, by logging to omega2 by serial console and using iwlist [INTERFACE] s
What type of wifi do you have? 2.4Ghz or 5Ghz? It's 802.11n only, 802.11ng mixed, or 802.11g? Omega does not support 5GHz and does not support 802.11n-only mode.
Do you use 802.11n wifi networks maybe? Omega2 does not support 802.11n (stated in documentation, which in wrong). You need to have 802.11g network. Remember also, that Omega supports 2.4Ghz only, does NOT support 5Ghz.
Maybe silly question, but... did you press ENTER in that console? Should login prompt show up after that.
Giving -1 and not giving alternative is so fair 
Using permanenty stored MAC is the only proposed solutions so far. Sure, you can reflash efuse (and change MAC). With that approach you will never find any unique id on any CPU that can't be altered (Intel tried it once and after EU commision intervention Intel abandoned idea of "serial numbers" in CPUs.).
Still, it's only way to get any unique ID based on hardware (accepting that, it can be changed by flashing efuse). If considering only out-of-the-box device, it can be assumed it's unique (for some purposes). I mean, when using new (own) device one should not be aware that someone in the middle changed efuse. If considering no-trust and 3rd parties, then id should be generated by software ("hard-to-guess" algorithms, uuid4 maybe?). Author did not reveal why and for what he needs that ID.
You can read original MAC address even if it was changed (change is not permanent). To read permanent (value from NIC ROM memory):
man ethool:
-P --show-permaddr Queries the specified network device for permanent hardware address.
Usage:
ethtool -P enp0s25
If you need to get it more programatically (C/C++), let me know.
PRid is not unique as global. It's just an identification of vendor + processor id (cpu type) + model revision. It's not unique in vendor's production line. It is not it's serial number.
Looks like your header is still wrong, see mine (2 first lines of my sample.py
#!/usr/bin/python3
# -*- coding: utf-8 -*-
Check if path /usr/bin/python3 is correct for omega (don't have one to check, right now).
@Zachary-Haslam
It's not omega dumb but your knowledge about Linux is not enough for now You need to add executable right on the file to execute it directly (chmod a+x /path/to/your/python/script.py).
Could you be more specific? What and how are you trying to start? Is it a python script? It so, look at its header line (#!/ like ) and change it to #!/usr/bin/env python3 or #!/usr/bin/python3 - check paths if they are correct for Omega2+.
Do not symlink like that, python3 and python2 are not compatible, and python is commonly identified as python2
@Zachary-Haslam
Use header in your script (first line):
#!/usr/bin/env python3
Then set executable right (chmod a+x /root/greeting.py) and run it directly:
/root/greeting.py
Just use as it was any other PC. Just use telnetlib, asyncio or any other library (may need to install package).
P.S. Remember to upvote answers if they fit your needs
Root cause is: netifd does support iface events UP and DOWN but does not support something like "up failure" (I mean, there is no event fired after iface connection failed, only for UP and DOWN). Afaik.
Indeed, MAC can be changed by e.g. ethtool.
You can use MAC address from network interface. It is unique.
Yes, Ethernet interface is already in your system. Board adds only phisical layer (M3066ANL votage transformer + RJ45 connector).
Look at https://community.onion.io/topic/1260/omega2-wifi-shut-down-apcli-link-down/7
You could modify my script to run in cron and check if it's connected to any AP and if not, restart wifimanager. Should help in your case.
Cron version would look like this:
#!/bin/sh
AP=$(iwconfig apcli0| awk '/Access Point: .*/ {print $5}')
if [ "$AP" = "Not-Associated" ] ; then
logger -t wifi-watch "WiFi not assosiated, restarting wifimanager";
ifconfig apcli0 up
wifimanager
fi
It's explained in root source (OpenWRT wiki):