Archer C7 V2 Did Not Boot After Scheduled Reboot

[SuperLid]

What version would you suggest I upgrade to?

[Lantis]

1.15.x, without preserving settings.
A log is needed to understand why it’s doing anything.

[SuperLid]

I'll look for that version and see how it goes.

[SuperLid]

I don't see that firmware at all. Can you send a link?

[Lantis]

https://lantisproject.com/downloads/gar ... XVsdCJdXX0

[SuperLid]

I upgraded to 1.15.x.

gargoyle_1.15.x-ath79-generic-tplink_archer-c7-v2-squashfs-sysupgrade.bin

Unfortunately, the wireless bridge function does not work at all. I have reverted to 1.12 at this point.

SL

[Lantis]

Well it most definitely does, but again I can’t help you without an attempt to gather information.
See how 1.12 works out for you.

[SuperLid]

I found that the UI setup was buggy as hell. There were fields that made no sense, when setting up client bridge. After refreshing the screen a few times, the fields changed to what I would have expected. After setting up with wireless config, I attempted numerous times to connect to the primary router, which did not happen. When I reverted back to 1.12, I connected without issue.

I was running 1.12 before and you said it was old, so I upgraded. I am having the issue I described, when I posted here, so you already know how 1.12 is working for me.

[Lantis]

In your initial post you list 1.11.0. So no, I don’t know how 1.12 would work for you as you don’t appear to have mentioned that version anywhere until just now. Maybe I’m reading it wrong or missing something, I apologise if so.
I’m not trying to piss in your cornflakes here. I’m willing to help but I don’t have any information to help you.

Like I said, wireless bridge is not the most stable of connection types. When it goes down you lose access to the router as there is no DHCP server running (it should be coming from upstream).
This is where the “dummy subnet” comes in and you can statically configure an IP in this range and get back in and fix it. This of course presumes the router is simply disconnected (or otherwise unable to connect) from the upstream network. If it is truly in some kind of boot loop or crashed state you won’t get far anyway.

So we need to understand what’s happening. Is it just disconnecting? If so, why? The logs might highlight something there.
This is also assuming you have correctly set the bridge up. Given you said it worked for a long time I haven’t questioned that.

As for 1.15 “looking buggy as hell”, that sounds classically like a browser caching issue. I would have recommended a cache clear to ensure that the settings had the best chance of being written to the router successfully. But let’s ignore that for now and stick with 1.12.

[SuperLid]

You are correct, I did say 1.11, but that was in error. I know how I made that mistake. So, I was running 1.12 and having issues after the scheduled reboot, which may be the case now, as I am back to square one.

Now, after the upgrade to 1.15, I was dead in the water, no connection to the primary router and a buggy wireless config screen. Sure, I can refresh the browser, but I have never seen that occur before, with 1.12 either. Why no connection to the primary router? I can try again and if no luck, what should I look for? The setup is exactly the same. I do have a backup of the config for 1.12. Can that be used to config running 1.15?

Thanks,

SL