gluon
gluon copied to clipboard
draft: ath79-generic: add support for TP-Link EAP225-Outdoor v3
This backports the TP-Link EAP225-Outdoor v3. Does it need to be tested again (merged to next in #2643)? If anyone is faster than me, feel free to help out!
- [ ] Must be flashable from vendor firmware
- [ ] Web interface
- [ ] TFTP
- [ ] Other:
- [ ] Must support upgrade mechanism
- [ ] Must have working sysupgrade
- [ ] Must keep/forget configuration (
sysupgrade [-n]
,firstboot
)
- [ ] Must keep/forget configuration (
- [ ] Gluon profile name matches autoupdater image name
(
lua -e 'print(require("platform_info").get_image_name())'
)
- [ ] Must have working sysupgrade
- [ ] Reset/WPS/... button must return device into config mode
- [ ] Primary MAC address should match address on device label (or packaging)
(https://gluon.readthedocs.io/en/latest/dev/hardware.html#notes)
- When re-adding a device that was supported by an earlier version of Gluon, a factory reset must be performed before checking the primary MAC address, as the setting from the old version is not reset otherwise.
- Wired network
- [ ] should support all network ports on the device
- [ ] must have correct port assignment (WAN/LAN)
- On devices supplied via PoE, there is usually no explicit WAN/LAN labeling on the hardware. The PoE input should be the WAN port in this case.
- Wireless network (if applicable)
- [ ] Association with AP must be possible on all radios
- [ ] Association with 802.11s mesh must work on all radios
- [ ] AP+mesh mode must work in parallel on all radios
- LED mapping
- Power/system LED
- [ ] Lit while the device is on
- [ ] Should display config mode blink sequence (https://gluon.readthedocs.io/en/latest/features/configmode.html)
- Radio LEDs
- [ ] Should map to their respective radio
- [ ] Should show activity
- Switch port LEDs
- [ ] Should map to their respective port (or switch, if only one led present)
- [ ] Should show link state and activity
- Power/system LED
- Outdoor devices only:
- [ ] Added board name to
is_outdoor_device
function inpackage/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua
- [ ] Added board name to
Signed-off-by: Philipp Rothmann [email protected]
As far as i remember the device support commits for the v3 weren't the only ones needed for supporting the v3 and there was a reason why the v3 wasn't alreafy backported to openwrt-22.03.
I think it had something to do with bumping the firmware-utils in OpenWrt which would also affect other devices etc.
Sorry that I do not have better news. I had looked this up at some point but then discarded the idea of getting support in 22.03.
What would be required to get support for the eap225-outdoor v3 is in my eyes:
- create a backport PR for OpenWrt which includes everything to get it working
- once/if that is merged, check if everything in Gluon works and fill out the checklist
- update this PR. It should point to master, not v2022.1.x, and if it's merged you can request a backport to v2022.1.x
I also took a look into the changes needed to get this device working in openwrt 22.03 and came to the same conclousion as @herbetom.
please also see the rules for device integration: https://github.com/freifunk-gluon/gluon/wiki/Device-Integration
No activity and targets the wrong branch (Device support has to first land in master). Feel free to reopen with a tested PR targeting the master branch.