av4625

Oh I don’t doubt what you are saying about the copy cat projects! My comment was more meaning people like myself asking questions to work through and solve the problems I am having. I had a couple of great discussions with people on the zero3 Armbian thread too, helping me out. Oh yea I totally get how the support thing works, and it makes sense. I was just looking for releases for when there was a maintainer and I know this also provides no guarantees, and I don’t expect any. Working through an issues is part of the fun and learning for me but I guess some people will just be rude if it has the odd problem. I can totally understand where you are coming from about people that just expect it to “just work”. Also the point you make about people profiting from your work, yea that would also drive me insane and tbh I don’t think if it was me I could continue to make it open source and watch that happen. But I am very thankful that you do keep it open source. That is a real pity about OrangePi. What other manufactures would you suggest would be better to look into as there are quite a few and I’m no expert with hardware and would end up picking a bad one again lol

For me the link from Werner was able to show me when the board had a maintainer. I then used the last build that was in that timeframe as I imagine it is maybe a little more likely to be reliable as someone was maintaining it then and there was likely people using it more often then too. Rather than automated builds (which are great that we have) that maybe less people use. Shortly after I bought an OrangePi Zero3 as wanted a bit more power to drive a Flutter GUI application.

These sorts of replies are a pity and I have had very similar ones on many of my posts on here just asking general questions. Like for example, I was looking for some info above, if it doesn't exist thats no worries but theres no harm in asking. They also likely put people off donating/contributing. But in this case a helpful reply from Werner got me the information that I needed and I am grateful. I'm sure I speak for a lot of people when I say I am super grateful for the work that you have done with Armbian and I bet its not easy to do or keep on top of for free (or even if you were paid). But it's a bit disheartening the amount of replies that contain comments about costs and about the person not contributing or whatever. We are just looking for help usually for our hobby from other like minded people that might have come across the same thing or know the answer that I don't. We aren't badmouthing you or anything to do with Armbian or demanding that you help us etc, and I'm really sorry if you felt I/we were. I'm sure you do get the odd person that isn't nice and is ignorant but I guess thats life, but I certainly wasn't being that way and I suspect that nobody above was either in this case. But stuff like this isn't nice or helpful when someone is asking a question: At the end of the day it is free to use (even if people are judged for not contributing) from the internet and if people have an issue they will likely ask on the forum and thats how they work together to solve/fix the problem. Theres plenty of great people on here that have helped me over the years!

This is exactly why I preferred to use network manager and you don't have to mess with dnsmasq and can use the default resolved and not worry about race conditions with them etc. Its also easy to use mDNS as its just setting a resolved conf value and a option on the network manager AP. dnsmasq-base should be enough, network manager seems to run its own instance of dnsmasq-base. I was also getting this, I also use a cheap uart to usb converter, but never had issues with it before. I have tried some of your previous suggestions too that I hadn't yet got round to yet. I built my own version of armbian, I chose Jammy and a server cli build as this is exactly what is on my working device. I wanted to see if the server image had something extra that I needed and didn't know about. I noticed that all the tiny differences I noticed with the debian minimal image were no longer there, like permissions differences with nmcli and by default on this image network manager manages the ethernet connection. Long story short, I still can't connect to a hotspot with a password on this image. All versions are the same as my working device so it must be a hardware difference. Probably the "hardware" bit here. I then tried the latest ubuntu server cli image (Oracular) on bleeding edge. It failed at the nmcli command to bring the connection up. Fails with a wpasupplicant error about taking too long to authenticate.

I started from a clean install just incase anything I did previously affected it, so NetworkManager is no longer installed. This directory doesn't exist for me now. Although the hotspot does work after reboots now, so it could have just been something I did wrong before but I was trying to be really careful and do. it all as you had in your earlier reply. I must have just been very lucky with the OPi Zero LTS as it "just worked" and seemed "easy" lol Its funny you say this, in my early attempts with network manager, when I listed all connections it never listed the ethernet connection and only my (broken) hotspot or when I connected to my router over wifi it listed that. So it seems like network manager never managed my eth connection, not sure what actually does.

I wont have a chance to look into it all until tomorrow, but does your setup use wpasupplicant? If so that rules that out as being the earlier issue

I have no idea what I did, that file didn't exist. I swear I put it there. I did the last 3 steps of the ansible file again after stopping hostapd and it now works! 🤯 I dunno if its mean't too, but it doesn't share the eth connection, so for example I can't access the internet when connected to it (the Zero LTS I have setup with network manager can without me setting anything up to do that). But I don't care about that anyway as it will live in a car and not be connected over ethernet after I'm finished dev anyway, just thought I'd call it out. Why my original way doesn't work and this does still baffles me 🤷‍♂️ I don't like not understanding why the other way didn't work lol But thank you a lot, I will try and research and learn more about hostapd and dnsmasq now so I understand it better.

Thanks for the help, my network knowledge is poor as you can likely tell. I did enable dnsmasq like the ansible file does and it seems to be running, but there is a failed log: ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/dnsmasq.service.d └─systemd-resolved-fix.conf Active: active (running) since Wed 2024-10-16 00:18:11 BST; 18h ago Process: 808 ExecStartPre=/etc/init.d/dnsmasq checkconfig (code=exited, status=0/SUCCESS) Process: 938 ExecStartPre=/usr/bin/systemctl stop systemd-resolved.service (code=exited, status=0/SUCCESS) Process: 941 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 946 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS) Process: 991 ExecStartPost=/usr/bin/systemctl start systemd-resolved.service (code=exited, status=0/SUCCESS) Main PID: 945 (dnsmasq) Tasks: 1 (limit: 4548) Memory: 5.1M CPU: 222ms CGroup: /system.slice/dnsmasq.service └─945 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service Oct 16 00:18:09 orangepizero3 systemd[1]: Starting dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server... Oct 16 00:18:11 orangepizero3 resolvconf[963]: Dropped protocol specifier '.dnsmasq' from 'lo.dnsmasq'. Using 'lo' (ifindex=1). Oct 16 00:18:11 orangepizero3 resolvconf[963]: Failed to set DNS configuration: Link lo is loopback device. Oct 16 00:18:11 orangepizero3 systemd[1]: Started dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server. hostapd status: ● hostapd.service - Access point and authentication server for Wi-Fi and Ethernet Loaded: loaded (/lib/systemd/system/hostapd.service; enabled; preset: enabled) Active: active (running) since Wed 2024-10-16 00:18:10 BST; 18h ago Docs: man:hostapd(8) Process: 814 ExecStart=/usr/sbin/hostapd -B -P /run/hostapd.pid $DAEMON_OPTS ${DAEMON_CONF} (code=exited, status=0/SUCCESS) Main PID: 853 (hostapd) Tasks: 1 (limit: 4548) Memory: 2.8M CPU: 265ms CGroup: /system.slice/hostapd.service └─853 /usr/sbin/hostapd -B -P /run/hostapd.pid /etc/hostapd/hostapd.conf Oct 16 00:18:09 orangepizero3 systemd[1]: Starting hostapd.service - Access point and authentication server for Wi-Fi and Ethernet... Oct 16 00:18:10 orangepizero3 hostapd[814]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Oct 16 00:18:10 orangepizero3 systemd[1]: Started hostapd.service - Access point and authentication server for Wi-Fi and Ethernet. I don't seem to get any logs from hostapd when trying to join the hotspot, it just shows this: $ journalctl -fu hostapd Oct 16 00:18:09 orangepizero3 systemd[1]: Starting hostapd.service - Access point and authentication server for Wi-Fi and Ethernet... Oct 16 00:18:10 orangepizero3 hostapd[814]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Oct 16 00:18:10 orangepizero3 systemd[1]: Started hostapd.service - Access point and authentication server for Wi-Fi and Ethernet. ip output: $ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 02:00:97:9b:cb:c0 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 44:fa:6d:94:c1:36 brd ff:ff:ff:ff:ff:ff $ ip -4 add 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 inet 192.168.178.170/24 metric 100 brd 192.168.178.255 scope global dynamic end0 valid_lft 839122sec preferred_lft 839122sec $ ip route default via 192.168.178.1 dev end0 proto dhcp src 192.168.178.170 metric 100 192.168.178.0/24 dev end0 proto kernel scope link src 192.168.178.170 metric 100 192.168.178.1 dev end0 proto dhcp scope link src 192.168.178.170 metric 100

I downloaded the latest image which has the same versions as you. This seemed to get a little bit further. I set it up manually using the exact files above just changing ssid and password as I havent used ansible before and couldn't get it to work. I am able to select the AP and type in the password and it seems to connect. But I get a no Wi-Fi symbol, this is no drama as I only want to be able to talk to the OPi using this hotspot to access a server it hosts. But, when I look at the connection, it doesn't seem to have a router/gateway IP. On my OPi Zero LTS where the hotspot works, I can SSH to the gateway IP (10.42.0.1 by default). Another weird thing the IP that my Mac got after connecting started with 169, I would have expected this to be in the range specified in /etc/dnsmasq.conf (dhcp-range=10.10.1.50,10.10.1.199,12h). I'm not sure if its just how this specific hotspot is configured but I guess yours works better than this. I dunno why, but I find hostapd and dnsmasq a lot more complicated and harder to understand. But I wonder, because this hotspot seemed to accept a password and my Mac showed it as WPA2/WPA3, is it just an option that needs to be set for the nmcli hotspot. Because without a password it works perfectly like I expect and I can SSH to the gateway IP etc etc. I also tried my own nmcli commands on the new image "just incase" but no luck.

Lots of replies here, thanks everyone! I tried specifying the channel, but it didn't help. I also tried 5GHz instead of 2.4GHz "just incase", but that didn't help either. You can see my config here: cat /etc/NetworkManager/system-connections/access_point.nmconnection [connection] id=access_point uuid=4eba9c88-d36f-40bb-a740-a9eeb903ca75 type=wifi interface-name=wlan0 mdns=2 timestamp=1728918559 [wifi] band=a channel=36 mode=ap ssid=TEST_TEST [wifi-security] key-mgmt=wpa-psk psk=password [ipv4] method=shared [ipv6] addr-gen-mode=default method=auto [proxy] One thing I noticed is that wpa_supplicant is showing UNKNOWN as the key management type which I thought was weird. sudo wpa_cli status Selected interface 'wlan0' bssid=44:fa:6d:94:c1:36 freq=5180 ssid=TEST_TEST id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED ip_address=10.42.0.1 p2p_device_address=46:fa:6d:94:c1:36 address=44:fa:6d:94:c1:36 uuid=82ce0d53-c98a-5bf8-b8a7-89759b194923 Haven't had time to try anything else yet

Unfortunately enabling WPA wont solve my issue as apple don’t allow/support it. I am only trying to connect from an iPhone or Mac. WPA works with nmcli commands without the need for hostapd and I can connect to it using WPA using windows. I tried the latest armbian release as it was slightly newer than the one I had, but no joy Next step is probably playing with the driver and kernel source code but that is a bit beyond my knowledge. I appreciate all the help though!

Just for info, the Ubuntu image that you can download from the OrangePi site also doesn't work The OpiOS fails to even setup a access point

I tried downgrading wpasupplicant to 2.9. The version from here: https://packages.debian.org/bullseye/arm64/ I also needed to get libssl1.1 from there as it is a missing dependency. This still didn't work even though this fixed the know bug for lots of users. I then tried downgrading network manager to the version from the link above and installing policykit-1 as it was a missing dependency. This also didn't work. I'm going to say that this is an issue with this specific board (and maybe others I'm not sure) and Armbian. There must be some issue in how ever WPA2 works. I read somewhere that some devices might store a key on the wifi/network chip and some don't. Maybe there is some difference like this with this device compared to the Orange Pi LTS. Sad

Haven't had a chance yet to follow the steps above but thought I'd update and say that I can't get iwd to work at all. Tried the steps here https://wiki.debian.org/NetworkManager/iwd under "Enabling IWD backend" and after doing that a `systemctl status NetworkManager` hangs indefinitely. It also hangs when trying to log in using the serial debug port and the red LED flashes quicker than normal. This is annoying as this normally fixes my issue for most people. To answer some questions above, I am using ssh over ethernet if I'm not using serial and the debug port. I also tried disabling and stopping wpa_supplicant when trying hostapd.

I will follow through this after the weekend. I didn’t even install network-manager when I tried. I just installed hostapd and vim from a clean install. I unmasked the hostspd service. I disabled the wpasupplicant service too. I used the conf file from the gist.github link. I just changed the ssid and password in the conf file. I had no issue with hanging with hostapd, just when trying to change NM’s backend in a different attempt and clean install.