Access point mode bricks RT-AC56U - 380.61

[Lordofdafood]

Since updating to 380.61 on my RT-AC56U. I am unable to use Access point mode. The router does not get an IP address so I am unable to get any debugging information out of the router from the admin panel. Devices connected to it suffer from severe degradation and packet loss.

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.

The only way I can currently use the router is to factory reset it and run it in Router mode. Any ideas? I would raise it as a bug but I can't see any official tracker for it

 

[pete y testing]

Since updating to 380.61 on my RT-AC56U. I am unable to use Access point mode. The router does not get an IP address so I am unable to get any debugging information out of the router from the admin panel. Devices connected to it suffer from severe degradation and packet loss.

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.

The only way I can currently use the router is to factory reset it and run it in Router mode. Any ideas? I would raise it as a bug but I can't see any official tracker for it

perplexed why the fw upgrade would kill ap mode but as a work around solution run the ac56u in tim's version of wan bypass mode

http://www.smallnetbuilder.com/basi...onvert-a-wireless-router-into-an-access-point

this will turn the ac56u into a switch and wap , its just an alternitive way to achieve the same ends

pete

 

[Lordofdafood]

perplexed why the fw upgrade would kill ap mode but as a work around solution run the ac56u in tims version of wan bypass mode

http://www.smallnetbuilder.com/basi...onvert-a-wireless-router-into-an-access-point

this will turn the ac56u into a switch and wap , its just an alternitive way to achieve the same ends

pete

Indeed, seems strange however I saw another topic floating around with someone having issues with AP mode on different hardware.

Ill try out the method you said a little later.

Cheers

 

[RMerlin]

I spent an entire evening recently working on something on an RT-AC68U (which is very similar hardware) while it was in AP mode without any issue. Use Asus's Device Discovery if you need to find what IP your AP has obtained.

 

[Lordofdafood]

I spent an entire evening recently working on something on an RT-AC68U (which is very similar hardware) while it was in AP mode without any issue. Use Asus's Device Discovery if you need to find what IP your AP has obtained.

Hmm strange,

I checked on my router and it wasn't listing as attached to the network, did a Zenmap and couldn't find it either. I wont need it as an AP for much longer so its not a major issue.

(I couldn't get to it in recovery mode when it was in AP mode, tried manually assigning the IP settings to the PC trying to access it also. The only way I could access it was using the WPS button to reset)

 

[RMerlin]

I checked on my router and it wasn't listing as attached to the network, did a Zenmap and couldn't find it either. I wont need it as an AP for much longer so its not a major issue.

Try Asus's Device Discovery tool, as your router might somehow have an IP in a different subnet. I think the tool works by locating any Asus device with a recognized OUI header.