![]() ![]() Yup, as suspected the AP100 only has the SoC radio and the AP200 image disables the 2GHz band on that so: uname -a You have to set either green or amber to off specifically to see that change.Īs an aside I noticed https is not enabled for luci by default and I thought that was supposed to be in 21.02? Interestingly the power LEDs seem to default to on. I would choose green for 1G and amber for 100M but that doesn't appear to be an option. ![]() I would choose just green on link by default there. The LAN LEDs still need to be present so that you can set them they just shouldn't use the net data trigger by default since both are always hardwired to flash. The Blue wifi LED is obviously wrong there. The LAN green and amber LEDs are defined and enabled by default but do not appear in the dropdown menu in the gui or in the filesystem: ls /sys/devices/platform/leds/ledsĪmber:power amber:wifi green:power uname -a Ok, finally had a chance to boot the AP200. Both radios can be either 2.4 or 5GHz and I'm just wondering if perhaps WG used them the other way around and the antennas are tuned for that. I'm not sure what the advantage is of keeping the same MAC layout that WG use. The MAC address in the ART the uboot is not used which still seems weird to me. Though I see other devices show as that for some reason. The SoC radio shows as Generic MAC80211 rather than Atheros AR9344 which it's shown as in the boot log. ![]() The default LED setting it set to trigger on eth activity but the LAN LEDs appear to be hard wired for that anyway so you get a sort of flashing on flashing action where the LED just lights less. The LEDs still list blue:wifi2g and ath9k-phy0 which don't actually exist. Have not tried flashing it yet, I assume that should work from the gui in recovery mode though? The new ramfs image looks good on the AP200. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |