It looks like iperf3 uses mostly one processor which peeks.
If somebody is looking for this device, it’s again available for 15€ at Mediamarkt/Saturn in Germany
I just installed the latest snapshot and it's working well, the only thing I miss is 160MHz support. Is it theoretically possible?
no not possible
Since this type of information is indeed missing, maybe we should add further information to the table of hardware. Docs are here about how to do it.
Hey, I'm trying to enter recovery, but unfortunately, I stuck on the boot process, I think.
I took the needle, pressed the reset button during plug-in, but red indicator is blinking, it's not going to orange, IP address is unrecognised, when I'm connecting the ethernet. Is it a hardware problem or Am I doing something wrong?
Red indicator blinking means the device has successfully entered recovery mode, orange color would indicate the firmware booting normally.
Maybe you need to assign a static IP address to your network interface, if you had not previously connected to the device while it was running running OEM firmware (which has DHCP enabled I think).
Just pick something like 192.168.0.123 with netmask 255.255.255.0, and you should be able to access the recovery at 192.168.0.50. Upload works better with Chromium than with Firefox.
That worked, thanks.
Was trying to assign it without router value, will try to flash it tomorrow or next week.
Additional information: on my devices, there is no ping response from the router in recovery mode. Looks like there is no ICMP support included. But the web interface for flashing the firmware was available.
Yes, the fact that it doesn't respond to
ping 192.168.0.50 cannot be emphasized enough — knowing this will save people a lot of time.
Thank you for all your work on the DAP-X1860 @RolandoMagico!
Since LED's are not working similarly to OEM for this device,
maybe following info will help anybody who might be interested in adding these features (I have no intention to add this myself and i do not think that led's are very important, but who knows. Maybe somebody else has a desire to make them work):
Which is the official path/tests to include a device on snapshot? - #11 by jdwl1o1
If the leds cannot be controlled you can explain that in the commit. Though fixed function leds will usually work without any setup. If they are not working in openwrt then they likely are addressable.
Usually that’s done in the dts or via an expansion bus module, that factory firmware should indicate how they are being triggered
We have all the allvailable LED GPIOs declared in the dts, they are controlled by the MT7621 directly, i.e. not addressable or requiring any separate driver (like e.g. Ubiquiti AirCube devices).
Except for the bootup blinking sequence, there is not much default LED behaviour in OpenWrt, except for Ethernet ports or (single band) wireless radios. Since this device has no separate LEDs for 2.4 / 5 GHz, I think there is currently no way of e.g. having a throughput indicator that covers both bands with a single LED. Also that is not what the OEM firmware would do, I think the Power / Status LED is just permanent on in normal operation?
What is the expected LED behaviour you would like to see in OpenWrt?
Just for the record. As I said, LED behaviour is low priority in my opinion, but if anybody were to work on this, then the following would be kinda expected: LED is green, instead of orange, if wifi is on/connected. Green is a signal colour for "everything is alright", whereas orange/red is a signal colour for "look out".
When i was running this device with OEM software, there were two things that stood out:
- When wifi was on (2.4 and 5 GHz were automatically configured to be on the same SSID), the leds were constantly shining in green light (no blinking, if i remember right. Just constantly on).
- There were blinking patterns for resetting and recovery mode (orange light)
Now with OpenWrt:
- When wifi is on; LEDs are constantly on, but with orange light.
- I would need to check, if blinking patterns for resetting and recovery mode changed, but i don't want to reset my current config
This refers to the RSSI bargraph LEDs, not the main / status LED with OEM firmware?
According to the OEM manual (and consistent with other DAP devices) there should have been a reg/green status LED, but for this device, there is only red / orange. The same is for the lowest bargraph display, it should have been red / green, but it was populated incorretly as well.
So only the upper two bargraph indicators can actually produce green light.
Maybe they will fix this in later versions? But I don't believe there will ever be another version of this one, and if they had fixed the LEDs with newer batches, you would see green instead of orange already.
In the meantime, just get a soldering iron and a bunch of 0603 green LEDs
Ah, got it. Thanks for the explanation!
I updated the preliminary device page to include the flash procedure, a picture and more hardware specs for this device . I also updated the "techdata" page to include more details and added wifi capabilities, which triggered an update of the table of hardware (toh). Is this enough to mark this device as "supported"?
I think it can be stated as
supported by now, even if this is only within the next release.
Many devices just list "snapshot" in the version / supported since column. When the release is out, we can still add the links for the final factory images etc.
Now supported by 22.03.04: https://firmware-selector.openwrt.org/?version=22.03.4&target=ramips%2Fmt7621&id=dlink_dap-x1860-a1
gluon folks did a backport to 22.03 (and fixed BMT remap-range to exclude UBI partition)
I wanted to thank all the developers for adding support for this device. It's cheap, pretty fast, compact, and already the snapshots have been rock solid for me. Now running 22.03.4 without issues.