Bug with initial setup page (QIS_Wizard)

[brbsh]

After updating to 388.2_2 on my RT-AX58U i got a bug with QIS wizard popping up after every reboot of the router.
I am using AX58U in AP mode configuration, so all ports may be in one bridge interface (including WAN) - so I am using port4 as uplink to my LAN
Before upgrading to 388.2_2 all was ok, after upgrade this message pops up if I want to login to web by router's IP (but if I go to http://x.x.x.x/index.asp all seems ok) and WAN LED on router became red.

 

[drinkingbird]

After updating to 388.2_2 on my RT-AX58U i got a bug with QIS wizard popping up after every reboot of the router.
I am using AX58U in AP mode configuration, so all ports may be in one bridge interface (including WAN) - so I am using port4 as uplink to my LAN
Before upgrading to 388.2_2 all was ok, after upgrade this message pops up if I want to login to web by router's IP (but if I go to http://x.x.x.x/index.asp all seems ok) and WAN LED on router became red.
View attachment 50436
View attachment 50437
View attachment 50438

What version did you upgrade from? If it was a 386 version did you do a hard factory reset after?

 

[brbsh]

What version did you upgrade from? If it was a 386 version did you do a hard factory reset after?

Upgraded from 388.2 (without _2), already did factory reset with config restore

 

[drinkingbird]

Upgraded from 388.2 (without _2), already did factory reset with config restore

Config restore or manually re-enter config?

If you restore, there is no point of doing a factory reset.

Are you sure your browser isn't filling in the QIS url when you start typing in the IP address/hostname?

 

[brbsh]

If you restore, there is no point of doing a factory reset.

After first reset I manually did initial config (DHCP client/WLAN settings) - but problem still here, after QIS did his job, my router rebooted and I saw him again
Then I just restored my config from file in QIS...
I think problem in port assignation, in AP mode logically it does not matter which port is used for uplink, and if I change port to WAN from lan4 I guess all will be ok (there maybe some messup with router operation modes in _2 release).
Problem is that my tiny patch cord did not fit well in WAN port with my setup (going from the right side and fits well only in LAN3 or 4)

 

[Tech9]

Use the WAN port for AP Mode. Your config restore is perhaps fine.

 

[brbsh]

Use the WAN port for AP Mode. Your config restore is perhaps fine.

But on fw 388.2 and older there was no problem with using AP mode with uplink from LAN port group, something has changed so far?

 

[Tech9]

In theory there is no difference, but I've noticed some Asus routers can't access NTP servers when LAN port is used in AP Mode. I don't know if it happens with some firmware versions only or it's router model specific. WAN port works always for some reason.

 

[drinkingbird]

But on fw 388.2 and older there was no problem with using AP mode with uplink from LAN port group, something has changed so far?

If you're not using aimesh it doesn't matter what port you use. In fact I prefer to use the LAN port due to some reports of WAN port oddities on certain models when running AP mode.

Maybe you've run into some sort of bug, haven't heard about it from anyone else. Guess you can use the WAN port or manually navigate to the index page.

Still think it could be browser related or perhaps after doing QIS (manually, not from backup) something did not save correctly or it needed another reboot etc. Then when you restored the config that just "locked in" the corrupted setting.

I'd do a hard factory reset (make sure it is the hard reset method, you can find instructions for each model on asus). Do the QIS manually again. If you get the setup wizzard after it "completes", try rebooting the router again.

 

[drinkingbird]

In theory there is no difference, but I've noticed some Asus routers can't access NTP servers when LAN port is used in AP Mode. I don't know if it happens with some firmware versions only or it's router model specific. WAN port works always for some reason.

On the other hand there were a couple models (XT8 maybe) that could not get full throughput when using the WAN port. Guess you're screwed either way. On the non-HND routers it just puts them all in the same bridge so shouldn't really matter, but not sure about the newer models.

 

[Tech9]

could not get full throughput when using the WAN port

I've seen this too, but don't remember model numbers. May be firmware specific as well. With Asus and Asuswrt you have to test all the time what works and what doesn't. Newer firmware is not always better. Newer routers are also not always better. RT-AC68U is the golden standard in my records.

 

[brbsh]

If you're not using aimesh it doesn't matter what port you use. In fact I prefer to use the LAN port due to some reports of WAN port oddities on certain models when running AP mode.

Maybe you've run into some sort of bug, haven't heard about it from anyone else. Guess you can use the WAN port or manually navigate to the index page.

Still think it could be browser related or perhaps after doing QIS (manually, not from backup) something did not save correctly or it needed another reboot etc. Then when you restored the config that just "locked in" the corrupted setting.

I'd do a hard factory reset (make sure it is the hard reset method, you can find instructions for each model on asus). Do the QIS manually again. If you get the setup wizzard after it "completes", try rebooting the router again.

UPD: Connecting trough WAN port did not solve the problem (still QIS and red WAN led), now rolled back to 388.2 without config reset, aaand... All OK, no red led on WAN and no QIS at all...
Seems like _2 has a bug with QIS in AP mode

 

[Tech9]

still QIS and red WAN led

This is strange because in AP Mode there is no WAN interface. If it works as it should in 388.2 and it doesn't in 388.2_2 - @RMerlin has to know about it. I don't think the changes between the two versions have anything to do with QIS and AP Mode though.