jovanpn

To people who is having same issue, I found possible solution for this version of TinkerOS. The problem was that dhcpcd5 software is accessing network interfaces before udev tries to set Predictable Names for network interfaces which actually blocks udev executing the change. So the possible solution is to delay starting dhcpcd service until udev completes its task. This is why network interfaces get their predictable names correctly when dhcpcd is disabled to start at boot. Possible solution includes creating a file at location: /etc/systemd/system/dhcpcd.service.d/override.conf with further contents: [Unit] After=network-online.target Wants=network-online.target After this file is created, dhcpcd service can be enabled to start at boot.

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.

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!

Hi @tooz thank you again for your effort. Unfortunately, nftables error remains. I now tried to write fresh Debian 11 image v3.0.11 on Tinker Board, then I applied your boot.2.img image, rebooted Tinker Board, then I updated the Debian with latest updates and then installed the nftables package. And in the end I started adding firewall rules and got the result from the picture below.

Hi @tooz thank you very much for your response and effort! I can confirm that now iptables work correctly. However, I still have problem with nftables and adding the rule: nft 'add rule ip mangle PREROUTING ip saddr != 127.0.0.1 tcp dport 8080 counter meta mark set 0x1' causes me to get the same error Error: Could not process rule: No such file or directory with pointers pointing to the counter word in the command. Maybe you could take a look at this article https://unix.stackexchange.com/a/667830 I found. First of all, I can live with iptables solution, but I thought to switch to nftables because it is now a default firewall since Debian 10. The reason I wrote about both errors (with iptables and nftables) is that I thought these two are somehow connected, but I see now they are not. One thing I noticed is that nftables package is not installed by default in this image file like it is described on Debian website. And I also tried working with nftables on fresh Debian 11 desktop installation on my PC which worked perfectly. nftables package was installed by default and I didnt have to configure anything with it, just add rules which all worked without any error. What is your opinion on replicating the same setup with nftables within the next release of Debian 11 for Tinker Board 2S?

Hi @tooz thank you for your response! UFW, as it is described by Debian Wiki page (UFW Debian Wiki page) is just a frontend for iptables, so I doubt UFW will be of any help. This seems to be a functional error and as I mentioned in my question above, some of the iptables modules are not loaded (or even not installed on the system). This same rule works fine on Debian 10 with kernel 4.19 (system image version 2.1.16). If I execute this command cat /proc/net/ip_tables_matches on both system versions, on Debian 10 kernel 4.19 I get a far longer list of modules than on Debian 11 kernel 5.10. Back in 2021 I had the very same problem with Debian 10 for Tinker Board 2S version 2.0.0 as I posted it here: and back then I got it resolved with new version of Debian 10 when it was released.

Hi, I'm trying to set firewall rules using iptables (tried also with nftables) but I'm having troubles with some options. I want to add this rule for example: iptables -t mangle -A PREROUTING -p tcp ! -s 127.0.0.1 --dport 8080 -j MARK --set-mark 1 but then I get error iptables v1.8.7 (legacy): unknown option "--set-mark". If I translate command to nftables: nft 'add rule ip mangle PREROUTING ip saddr != 127.0.0.1 tcp dport 8080 counter meta mark set 0x1' then I'm getting error Error: Could not process rule: No such file or directory which points to the counter word. After some extensive research, it seems that some modules are not loaded. Is someone familiar with this problem and are there some solution with this Debian version or I will have to wait for some new Debian release?

Any update on this topic?

Hi @tooz, thank you for your reply. I'm talking about Debian 10 OS and there is only v2.0.0 available for download for Tinker Board 2S. Is there v2.0.1 available somewhere else?

Hi, Im having both, Tinker Board S and Tinker Board 2S boards and Im having very strange problem with iptables (legacy) version which came with Tinker Board 2S. Although they say they are the same versions on both boards with the latest OS versions (3.0.11 for S and 2.0.0 for 2S) something is different or something in Debian OS is making problems on 2S board with commands Im trying to execute. For example, if I try to execute this command on 2S board iptables -t mangle -A PREROUTING -p tcp ! -s 127.0.0.1 --dport 8080 -j MARK --set-mark 1, I get error that --set-mark option is unknown, while executing iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080 command, Im getting error that --to-port option is unknown. Both commands work perfectly on S board. Does anyone know what could be the issue here and maybe possible solution as well? Thanks in advance.