ansible-openwrt
openwrt-build
ansible-openwrt | openwrt-build | |
---|---|---|
8 | 1 | |
335 | 12 | |
- | - | |
0.0 | 5.9 | |
about 1 month ago | 6 months ago | |
Shell | Makefile | |
GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ansible-openwrt
- Configuration as code for OpenWrt installation
-
Has anyone ever used openwrt with ansible?
you can use this: https://github.com/gekmihesg/ansible-openwrt
- Using ansible on host without python installed
-
OpenWrt 22.03.0 Released
There have been efforts in that direction:
- https://github.com/gekmihesg/ansible-openwrt
- https://github.com/NN708/ansible-openwrt
and even
- https://docs.ansible.com/ansible/latest/collections/communit...
Are they not sufficient?
-
Would you recommend Ansible to manage targets without python?
https://github.com/gekmihesg/ansible-openwrt (which is a dependency of the nn708 one) to me seems way better, but it works by re-implements various ansible modules in a way that doesn't require python, which - while commendable in principle - will in practice surely drive users into hard-to-deal-with issues with incompatibilities, unsupported features, etc (of course the details of the re-implementation of modules are not documented, so it's gonna be trial, error, and.. hope the next release doesn't break things).
-
Can Ansible interface with a microcontroller (Arduino, Pi pico)?
One good example is this collection to manage OpenWRT (still uses ssh, but the modules it provides are all in shell) https://github.com/gekmihesg/ansible-openwrt
- Use OpenWrt access points together with ubiquiti APs, centrally managed from the same controller?
- Can you clearly articulate why using Ansible to run shell scripts is a bad practice? Is it?
openwrt-build
-
OpenWrt 22.03.0 Released
> A pain point in upgrading the OS is that packages that were previously installed need to be reinstalled.
Which when you start having lots of OpenWRT based devices kinda gets a pain. And we hackers we solve pains, don't we? ;)
So when a new OpenWRT release hits the market, I usually just have to update the OpenWRT release-number at the top of my makefile, and Github builds all the images for all my devices, with all the packages and customizations I already have in place.
All devices upgraded in less than 30 minutes.
My setup, for those interested: https://github.com/josteink/openwrt-build/
What are some alternatives?
openwrt-configuration-ansible - OpenWrt configuration for router + dumb access points with Ansible playbook for centralised management
openwrt - This repository is a mirror of https://git.openwrt.org/openwrt/openwrt.git It is for reference only and is not active for check-ins. We will continue to accept Pull Requests here. They will be merged via staging trees then into openwrt.git.
CentOS7-CIS - Ansible CentOS 7 - CIS Benchmark Hardening Script
ansible-openwrt - Ansible collection to configure your OpenWrt devices more quickly and automatically (without Python)
ansible-openwisp2 - Ansible role that installs and upgrades OpenWISP.
wrt32x - OpenWRT firmware autobuilder for Linksys routers
ansible-backup - Ansible daily backup role
openwrt - This repository is fork from openwrt official repo, we will update the latest tag and release GL.iNet firmware based on it.
ansible-playbooks - Playbooks for automating server procedures based on our Community guides
asuswrt-merlin.ng - Third party firmware for Asus routers (newer codebase)
salt_openwrt - Saltstack openwrt proxy minion
packages - Community maintained packages for OpenWrt. Documentation for submitting pull requests is in CONTRIBUTING.md