I popped down to the local tech recycler and picked up a venerable Linksys EA6900 (v1.1) for $4.20 to repurpose as a client bridge for this stack of servers I’ve got heaped up in the back bedroom, to be confronted with this peculiar installation procedure for dd-wrt firmware:
-obtain oldest possible linksys firmware 161129;
-obtain linksys “tftp” abandonware utility from archive.org;
-ping 192.168.1.1 -t and watch for TTL 100;
-after about 25 pings, hit “upload” on tftp;
-repeat if timeout, retry if boot succeeds;
-login to diagnostics and revert to the older version on the alternate partition;
-repeat all that first step so both partitions are the same;
-now reset to factory defaults;
-now obtain dd-wrt #23194 dating from Dec 22, 2013;
-manual update firmware to that one;
-repeat again for the second partition;
-administration / factory default again;
-now you can pick which iteration to choose, whether the “Kong” or the “brainslayer” edition (I couldn’t decide so I just picked the latest June 12 2023 version);
-to be confronted with the bootup sequence followed by “Linksys” lamp flashing off and no response to telnet, ssh, or WebGui! “Brick,” except it’s responding to the ping -t with TTL 64.
-power cycle 3x with 10 second pause each time while crossing fingers & toes will trigger the second boot partition, except obviously, no.
-ULTIMATELY, after farting around hard enough, I discover it’s merely ignoring the WebGui request when stated as “https”. Deleting the “s” reveals the damn thing really was running, the whole time.
-