jovanpn 0 Posted September 17 Hi, we are using Tinker Board 2S for quite some time already and also been using it with hostapd software to use it as hotpost AP at some point. But we noticed with last 2 or 3 OS versions that we have a problem with this setup. The problem seems to appear, in more than 95% of cases, when hostapd application is enabled to run after the OS is started up. When this is set, then wireless interface name is not being renamed wo wlp1s0 but it remains as wlan0 and in this case hostapd cannot run properly. What could be the cause of this problem and how I could fix it? Thanks in advance! Share this post Link to post Share on other sites
tooz 55 Posted September 18 hello @jovanpn, could we have the logs and/ or steps to repro the issue? Share this post Link to post Share on other sites
jovanpn 0 Posted September 19 hello @tooz thank you for your response and sorry for my response delay. As I wanted to prepare the steps for you to reproduce the problem I did some tests and I figured out that it is actually dhcpcd5 apllication that's making the problem and not hostapd. I dont know if you can rename the topic to use dhcpcd5 app name instead of hostapd. Regarding the problem with dhcpcd5 app, I'm not providing the logs because you can reproduce the problem very easily in few steps and it works always. You just need to flash Tinker Board 2S with fresh TinkerOS image version 3.0.25 and do next two commands: sudo apt update and then sudo apt install dhcpcd5. When everything is installed, you can reboot the tinker board and then next time wifi interface has the name wlan0. If you disable dhcpcd5 service starting at the start using command sudo systemctl disable dhcpcd5, wifi interface gets correct name of wlp1s0 from the next OS start. So the problem is that if dhcpcd5 service is installed and it is set to start at the OS startup, wifi interface gets wlan0 as a name and you cannot use wifi. If dhcpcd5 service is not set to start at the OS startup, wifi interface gets name wlp1s0 and everything is fine. Also One note though of what I noticed to happen. When Tinker Board is started for the first time after OS is flashed, if you just login to the OS and do one reboot, then the wifi interface gets the name of wlan0. And with every next OS start everything works as normal (wifi gets name wlp1s0), so only at 2nd OS start wifi gets wrong name. Also, this first time OS is started after fresh install, updating apt list doesnt work immediatelly. I had to repeat the command few times and maybe use apt update command without sudo to trigger something what will allow sudo apt update the next time. Share this post Link to post Share on other sites
