mediatek-filogic: add Cudy AP3000 Outdoor v1

[blocktrron]

• 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)
  • Gluon profile name matches autoupdater image name
    (lua -e 'print(require("platform_info").get_image_name())')
• 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#hardware-support-in-packages)
  • 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)
    • if there are multiple ports but no WAN port:
      • the PoE input should be WAN, all other ports LAN
      • otherwise the first port should be declared as WAN, all other ports LAN
• 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
• Outdoor devices only:
  • Added board name to is_outdoor_device function in package/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua
• Cellular devices only:
  • Added board name to is_cellular_device function in package/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua
  • Added board name with modem setup function setup_ncm_qmi to package/gluon-core/luasrc/lib/gluon/upgrade/250-cellular
• Docs:
  • Added Device to docs/user/supported_devices.rst

[Djfe]

I don't think it's wise to keep adding further (mt7981) devices while their wifi is unusable with Gluon after just 1-3hours of uptime.
TQ in wifi mesh drops to 1-3% (when it was 100% in the first hour of uptime)

Please keep using the device and its wifi for a couple of days to confirm, whether it doesn't happen for this one.
We would love to roll out filogic in Aachen but the target's wifi (atleast mt7981) proofed to be too unstable for that.

[autinerd]

We already have a node to test: https://map.freifunk-stuttgart.de/#!/en/map/80afca55801f, which is running for 30 days now and seems to work without issues, also the meshing TQ looks good.

[herbetom]

Until there is a completed checklist i would propose marking this as a draft.

[Djfe]

We already have a node to test: https://map.freifunk-stuttgart.de/#!/en/map/80afca55801f, which is running for 30 days now and seems to work without issues, also the meshing TQ looks good.

okay TQ doesn't look particularly bad but I assume your firmware runs modprobe every 12hours to reload the wifi firmware mt7915 onto the mcu chip.

seems to work without issues

Sounds like you haven't used the device yourself so there might've been issues. Like for us.
There are no error messages in the log for these issues sadly. You have to use the AP yourself to confirm whether it runs smoothly for days.

Yes it does traffic, I can see that. Awesome! :)
but that doesn't mean the user experience can't be bad at the same time.
We got very weary regarding these because they ran unstable for us. (unlike ramips-mt7621 which only had outages from time to time (mcu timeout because it hangs), filogic runs unstable for us without actual outages, which is worse)

edit:
#3305