It looks like your 2.4GHz radio isn't working with that build though? Which is an issue I'm also having atm. Both 5GHz radio are up and connected but 2.4GHz isn't happy.
There wasn't anything wrong with 2.4GHz in the end
However, my radio2 keeps choosing channel 128 when set to auto and in this state nothing will connect to it. Not sure what the issue is there but it works if I force it to channel 108.
No, but I haven't tested it so I preferred to give you the exact steps that worked for me. I never used 2.0.6 firmwares because they have a NAT loopback bug and mapping ports 80 and 443 to an internal device kills your access to the router from the LAN as it directs you to this other internal device. Why the router would do NAT loopback on a connection coming from the LAN is something that only Linksys engineers could explain.
I haven't tried a VLAN as such but I have set up an isolated guest wireless LAN if that is what you are after. You could also remove one of the wired ports from br-lan and add it to the guest network.
You can manually switch to boot the other partition. Turn on the router, when the light goes on count 10, then switch off and wait for the led to go off. Do that 2 more times. That will tell the router that it has been unable to boot 3 times and switch to the other partition.
It's basically this: https://www.linksys.com/support-article?articleNum=316324
I did the same as @mgupta80 and tried this. I'm sure it worked, in terms of switching the partition (since the SSIDs I'd set up on OpenWRT disappeared), but the default SSID didn't start broadcasting. Any thoughts?
I was wondering if it's possible to re-flash using TFTP, but guidance seems to suggest you need to know the TFTP client or server IP, so not sure if this is practicable.
EDIT: flashing over TFTP worked nice and easily, it would seem. Easier to start from scratch!
This was bad info so removing (thanks @lytr). Best bet is using failsafe mode, turns out. There are no LED indicators (at least there weren't for me), so you have to just spam the reset button when you turn it on - I did it for about 10 seconds - and then try SSHing in again.
For me, it did indeed switch after 3 failed boot attempts, but the original SSID didn't then start broadcasting, as I say. As such, I was unable to access the control panel to flash the new firmware, and of course the manufacturer disables SSH so that wasn't an option either. Hence resorting to TFTP.
I really didn't want to start disassembling anything!!
Agreed on the USB suggestions - I didn't realise you could do that.
Hmm. I now can't reproduce what I did before, @lytr . Perhaps it was somehow a fluke, but I don't know how I regained access to the device otherwise... I tried entering failsafe mode, but thought it had failed - perhaps it didn't and I actually got access that way, accidentally? I'll try a few things and report back.
Hi @lytr@Digitiain, It turns out the failsafe mode does not works for me. I have opened the router but it does not have pins. I have attached the photo of the cable that I currently have for serial access, do I need a different cable for this router?