Can't login on .34

[Anders]

It might have been answered before, but I can't find it on "search".

After updating to .34 everything is working, but I can login anymore.

Has my password reset to standard, and what is the standard password?

Even with admin/admin I can't login

Br

Anders

 

[RogerSC]

Have you cleared your nvram (gone back to factory default settings) after the firmware upgrade yet? You can try powering down your router, and press the WPS button before you power the router on. Keep holding the WPS button for a few seconds (maybe 15 seconds or so) while the router powers on, then release the WPS button.

Now you should be back to factory defaults, with the admin GUI at 192.168.1.1, and the factory default admin login is user "admin", password "admin".

 

[RMerlin]

Asus goofed with their recent anti-DDOS code they added to the web server, which falsely triggers when software/devices on your LAN try to blindly connect repeatedly to its port 80.

 

[jlake]

I was also locked out of 34_2 GUI. Telnet and reboot fixes it.

You may need to power cycle the router if Telnet isn't enabled.

 

[primitivo]

I am also facing this issue on 34_2. It won't let me login after some time of working. It's horrible.

RMerlin any quick-fix that you can apply for this behaviour?
If not, time to go back to 33.

 

[RMerlin]

I am also facing this issue on 34_2. It won't let me login after some time of working. It's horrible.

RMerlin any quick-fix that you can apply for this behaviour?
If not, time to go back to 33.

You will have to figure out what is actually constantly trying to connect to port 80 of your router.

One temporary workaround would be to disable HTTP access and only enable HTTPS - that will be on a non-standard port (8443) which should be fine.

To immediately regain access to the router, you have to restart the httpd daemon. Through telnet or SSH:

service restart_httpd

Then immediately log back in to modify HTTP access.

I have already disabled that bruteforce protection feature in my development code, so next release should be fine regardless of whether Asus fixes it in the mean time or not.

 

[saulos]

thanks Merlin,
this solve my problem too