Historically DD-WRT has been faster at updating for hardware changes, country code restrictions, etc. than OpenWRT/LEDE. I'm not sure why that is.
I work as an IT consultant and often stock a couple of Archer C7s for installation at client locations. When the last C7 I ordered showed up as v4, I went looking to see if I could find a different device that was currently supported. I discovered that the Archer C2600 has stable LEDE support.
In my testing, between the 4 antennas (better beamforming) and the improved signal processing of 802.11AC Wave 2, I am I have almost twice the usable Wi-Fi coverage area. At the limit of where the Archer C7 signal disconnected I can now push 40 Mbps (my WAN maximum) over both the 2.4 and the 5 GHz bands.
So even though I would like support for the Archer C7 v4 so I can use the one I have sitting around, I am going to be switching to the C2600 for everything going forward.
@kanedias Sure, Felix does a lot for the community, but he lives in Germany AFIK, so a US-locked C7 v4 might not be of much use except as a test bed.
I also send my heartfelt thanks to Felix and all the others for their work on LEDE.
Given that the device support patch isn't quite trivial (new mach file, rather than just some tweaked image options), it's not very likely to be backported to 17.01.x (changes like that would violate the roughly agreed upon backporting guidelines, of course it's always possible that a developer might look another way…). It will however be part of future releases (18.x.y) and obviously is already part of the development snapshots.
Ive noticed that the LED for the LAN and WAN are out of alignment. WAN LED is always on, when plugging a cable into WAN the 4th LAN port LED lights up, Cable in 4th LAN lights up 3rd lan and so forth. Any one else notice this?
I have a EU version and ... I couldn't get the webUI.
Both radios were in managed mode... So I decided to go back to stock firmware and this is were I bricked the device.... I was stupid enough to think that sysupgrade wants the .zip file...
The de-bricking procedure for the Archer C7 v1/v2 might also work with the v4. Basically, the system has a built-in restoration mode that, when invoked, uses TFTP to download and flash a new firmware file from a specific IP address.
Yeah, so I did that. Apparently I am too stupid to configure LEDE easily in command line.
So using tftp I could revert to the stock firmware. At least the router is working now...
I have had that feeling several times when working with LEDE, but if you can manage a TFTP restore you can manage to install a developmental snapshot and then add the web interface. It is as simple as connecting via SSH to the device and running the following two commands:
opkg update
opkg install luci
You will then have a functional web interface, from which you can make any other changes you like.
PS. I prefer to use opkg install luci-ssl, which enables a HTTPS web interface.
Latest snapshot results in my LED behaving oddly. even with 1 cable connected into the LAN all led are solid on and dont blink when there is traffic activity.
