I am new to this forum and also to OpenWRT and also with a new router D-Link DIR-2660. I found out it is a A2 version. I reseached this forum a lot in order to install OpenWRT on the router. Thank you very much for all the posts and inputs. Maybe my findings can also help somebody in future - I wrote it from a beginners point of view, like I am, thanks for understanding. I added the references I used at the bottom.
Thank you very much
My steps done:
Connect PC to D-Link DIR-2660 A2 (LAN Port) with a LAN Cable
Great it worked for you, these devices are indeed a little cumbersome at the moment.
As far as I recall, we don't have the RSA keys to allow flashing via OEM webinterface for this device, but the latest official OpenWrt snapshots (not v21 though) already have the headers fixed, so that the factory image will at least work for the Recovery. However, official snapshots don't come with LuCI (unlike some custom-built images provides by users).
In any case, I would still recommend you to sysupgrade to the latest official 21.02.01 release, this also allows to install packages via opkg later.
@Lucky1 could you confirm that the change in headers only applies to the factory image? So the sysupgrade to v21 (with missing headers) would be safe, or could there still be issues after reboot?
When you say OpenWrt snapshots (not v21 though).....which snapshot are you referring to please? When I go to the firmware selector to download it just shows 1 snapshot available (ce2b8e6de5897a260a7ebb77e968953ba2890849bb5924b169e07b4e17e9acec)?
Can I sysupgrade from the snapshot factory image to the latest official 21.02.01 release (subject to the headers being ok) ?
Yes, that one (hash changing every day though) can be installed via the recovery. But it does not come with LuCI, so you have to install it later as described by @Peer in the first post (just connect the WAN port to your local network to allow opkg to download the packages).
As it just turned out, none of us actually seemed to have tested this exact situation (i.e. whether it would still reboot correctly after flashing, without the headers fixed), but it should most probably work.
Besides, nothing can go wrong, since you can at any time repeat the factory flashing via the recovery and be back to a working system. We'd actually be curious for someone to verify that reboot works with v21, since the patch fixing the headers will only be included with the v22 release.
It's a dynamic DNS hostname, probably his machine isn't running at the moment or has no connectivity.
the master snapshots have the new header but the 21.02's snapshots won't
I have a feeling if you sysupgrade to a version without the correct header header info it won't boot
but I'm not 100% someone will have to test and report back
I'm sure you will be able to recover back to a factory or oem image
someone could try to open a pull request to update 2102 but as it tool 6 months V22 will be branched by then
I flashed the DIR-2660 successfully. Label on rear of router says hardware version A2 although D-Link software says it's A1.
Seems like there are a couple of options (at least) to get the device flashed and I did consider flashing with current factory snapshot and then doing a sysupgrade using the official release; it seems like the headers in those files would support flashing to the DIR-2660 (I did check them) and I assume upgrading from snapshot to official sysupgrade would work (given headers are correct).
However, in the end I decided to go with path of least resistance and I flashed with the file Lucky provided (21.02.1) and it worked perfectly. I did use safe browsing in Firefox, not sure if that was required or not but it worked.
Thanks for your help and to @Peer for the initial write up
V22 & master has the updated header
but if you update to V21.02.3 & you model needs the updated header
then it just wont boot that image
but you should be able to get back to the recover console
and flash one with the header
it may even place you into the recover console