Global Moderators

@MK thanks, yes I saw your time clock gizmo, nice piece of kit. Congratulations.

@Lazar-Demin The reason why I think a PoE version would be useful is as @MK mentioned, getting power to devices is often a pain, I think especially in a development of IoT devices I want to test devices in various locations and honestly I prefer to cable my stuff for reliability as WiFi is not often reliable in some locations. Especially when I'm fixing things to walls or up in the ceiling of a building where cables, metal and fluorescent lights may be found. Getting an ethernet cable to some of these locations can be a challenge, but getting power there as well can get really complicated and expensive.

I also think a solid reference implementation for use with Omega2S+ would be a bonus, or even better with the Omega3S+

Just the inclusion of the ETH port will save new players a load of headaches when they invariable screw up the firmware I also like that users can start off with the Omega2+ and as they progress and need access to greater functionality the Omega2S+ version exposes the full set of UART, GPIO and PWM.

I anxiously await the version that included PoE

https://www.crowdsupply.com/onion/omega2-eval-boards

@mauriziomeucci While I have no idea of the decision making process, perhaps some clarity can be found in the heading of the release announcement: "Major Beta Firmware Update: OpenWRT 23.05 ......"

The term "Beta" indicating that it is a test release inviting feedback, which would include which packages users may prefer to be included. Personally I don't include avahi in my custom builds.

Added a FAQ

While OpenWrt is a single user system, you can create additional users so you don't have to disclose the root user password. You can add the user by editing /etc/passwd and /etc/shadow or you can install the useradd package:

opkg install shadow-useradd

Now add a new user named "admin", but we don't want them to have shell access:

useradd admin -d /var -M -s /bin/false -p mytemporarypassword

The password is added in cleartext so you need to change it using the command:

passwd admin

Follow the prompts to set your password then you can confirm the new user has been added as required:

cat /etc/passwd
cat /etc/shadow

Since OnionOS uses ubus via rpc we need to add the user to the rpc user list. The configuration file is /etc/config/rcpd, but you can use uci commands to add the user:

uci add rpcd login
uci set rpcd.@login[-1].username='admin'
uci set rpcd.@login[-1].password='$p$admin'
uci add_list rpcd.@login[-1].read='*'
uci add_list rpcd.@login[-1].write='*'
uci commit rpcd

The username must match the username we just created and the structure of the password field causes the rpc daemon to use the system password we just created.

The "read" and "write" fields is set to an asterisk indicating that the user will have unrestricted access, the same as the root user.

You can confirm the new user had been added using a uci command:

uci show rpcd

rpcd.@login[0]=login
rpcd.@login[0].username='root'
rpcd.@login[0].password='$p$root'
rpcd.@login[0].read='*'
rpcd.@login[0].write='*'
rpcd.@login[1]=login
rpcd.@login[1].username='admin'
rpcd.@login[1].password='$p$admin'
rpcd.@login[1].read='*'
rpcd.@login[1].write='*'

Now restart the rpc daemon:

service rpcd restart

You can now login to OnionOS with the same functionality as the root user has, but the user has no console access.

@Lazar-Demin I'll put something together as a FAQ. Might take a few days to have the time.

@MK OnionOS / OpenWrt is a single user system, you can install a package to permit creation of users ad groups. So then it comes down to the permissions you create on whatever package you want to use. I haven't used the OnionOS stuff for a few years but as I recall it uses the the ubus acls ( @Lazar-Demin might correct me ). I use it with mod-ubus, here are my steps to create a user named admin:

# Setting up for mod-ubus (php configuration)
cd /usr/share/rpcd/acl.d/
vi adminuser.json

{
        "adminuser": {
                "description": "Administrative user access role",
                "read": {
                        "ubus": {
                                "session": [
                                        "access",
                                        "login"
                                ]
                        },
                        "uci": {
                                        "system": ["timezone", "zonename"],
					"wireless":["*"]
			
			}
                },
                "write": {
                        "ubus": {
                                "*": [ "*" ]
                        },
                        "uci": {
					"system": ["*"],
					"wireless": ["*"]
                	}
		}
        }
}

#add entry to /etc/config/rpcd
config login
        option username 'admin'
        option password '$p$admin'
        list read adminuser
        list write adminuser

#update /etc/passwd
admin:x:200:200:admin:/var:/bin/ash

#update /etc/shadow
admin:$1$6Foyv2Pv$G/P624gFKZWld7YZkpQdP1:18278:0:99999:7:::

#set the admin user password using passwd command


/etc/init.d/rpcd restart

Take a look at these files on your system and see how it's currently being used.

@Lazar-Demin I haven't used overlays but I just checked what files it can create, you can see the options here:

Since OpenWrt is OSS you can download the community version of CLion and give it a shot.

The docs are here

Thought it was worthwhile to make members aware that CLion IDE by Jetbrains supports code completion for DTS and DTSi.

This was news to me, I've always done this manually, but CLion makes it sooooooo much easier.