378.55 on both AC66U and AC87U and cannot login anymore

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Swiso

Occasional Visitor
When you are running in AP mode, the WAN port is just like the other LAN ports, no difference.

Since you are able to ping the routers, the networking looks good. Unfortunately, we can't get in to look at the syslogs to see what may be happening..but my guess is that the web server is down or not starting correctly.

My next step would be to try this....

Unplug each of your clients (not the powerline/switch interconnects) and then reboot the routers and the netgear switch. Replug you primary client you've been testing from and see if you can get to the gui's then. If you can, immediately go to the Administration > System page and enable telnet and apply (so maybe we can collect additional data later).

Then plug in each client one at a time and retest. As you do this, on the AC87, don't use LAN port 1, it has a special setup and I'd like to eliminate the most variables possible.

There was just another user where having an HP Printer plugged in was apparently causing the router web server to crash (still don't understand that one), so may want to save that one for last.

Ok, I will try this tomorrow....3.45am..time to go to bed :)
Thank you very much !
 

wireless

New Around Here
Hello,
I have similar problems:

Here's my configuration:
1. Cisco RV320 router as a WAN gateway
2. RT-N66U connected to it and working in AP mode (2.4GHz disabled, only 5GHz enabled)
3. 4 x RT-N66U working in media bridge mode, connected to #2
4. ALL RTs are configured to get their IP numbers from DHCP server
5. they have assigned fixed IP addresses to their MACs in my DHCP server
6. DHCP server, which I use is ISC (I use combination dhcpd/bind on a linux machine, connected to #1)

No other wireless clients connected to my RTs (they are used ONLY to distribute wired network connections across my home)

All RTs have 378.55 Merlin firmware. Factory reset after this firmware installation DONE to all of them

a. After some time (from few hours to few days) some of child RTs "dissapears": their web interface is not accessible, they DO NOT respond for PING.
b. In MOST such cases wired devices connected to them respond for ping, and work OK
c. In SOME such cases wired devices connected to them dissapears as well (they do not respond for PING, they do not see network)
d. there has been 1 (one) situation, when my parent RT has dissapeared in such way

Combinations of #a and #b are significantly more frequent, than combinations of #a and #c

In #d situation all the child RTs dissapeared as well. Restart of parent RT has helped.

When this sitation appears, there is no any entries specific to such dissapearing device in any logs, including DHCP log file

After restarting parent RT problem dissapears for some time, and then - after some time - appears back again
After restarting such dissapearing child RT problem dissapears for some time - and then - after some time - appears back again, but - sometimes dissapears the same child RT, sometimes - other one.

There is a SINGLE ONE child RT, which has never (up to now) dissapeared.
All the child RTs have, of course, the same configuration, applied to them, using web interface.

It looks, like my parent RT could not handle more than 2 child RT working in media bridge mode, when only two child RTs are ON, everything seems to be OK, however - it is MY IMPRESSION ONLY, it is POSSIBLE, that such situation would appear in that case after some more time.

And - BTW - my 5GHz network is the only 5GHz wireless network, which I see.
My 5GHz network is secured by WPA2-Personal/AES method.

And - additional note: I have tried to configure them to do not use DHCP at all, and - instead of this - assigned their IP directly to them, but it has not helped. Such situations seem to be totally not related to DHCP.

Thanks
Wireless
 
Last edited:

martinr

Part of the Furniture
I think I definitely not make that operation.

I remember that after updating the firmware, I did login to both routers and changed some settings. ( wireless channel bandwidth for example)
But did not restore to default settings.

I believe, and John will correct me, that by updating from stock Asus firmware to Merlin's firmware WITHOUT restoring to factory default settings afterwards, you are probably wasting your time with further fault finding. I think you will have to restore to factory default and then re-enter your settings, if only to eliminate this mistake as the source of the fault.

As Merlin writes: "If you fail to do a factory default reset, then your router will still have the old values, and it will keep using them. That can lead to performance issues (especially in changes related to the wireless driver), or flat out odd behaviour (if one of the settings no longer works the same way as before)."

How to reset? Merlin again:
"If your router fails to boot due to corrupted/invalid nvram settings, then you will have to turn off the router, press the WPS button (on Asus routers), then turn on the router. Wait about 10 seconds, then release the WPS button. If the router is booting correctly, then .......While router is running, press the reset button for about 5 secs, then release it. Router will then reboot.".

Paragraph 10 for the reset button in: Ihttp://www.asus.com/support/FAQ/1005484/


(Note: it generally isn't necessary to restore to factory default when updating from one Merlin version to the following one; however, sometimes it is necessary eg when 378.51 was issued. Nevertheless, Merlin states when a restore (reset) is required. Certainly, when going from stock Asus to Merlin's firmware, restoring the settings to the factory default state must be carried out, not to do so is asking for trouble.)
 
Last edited:

john9527

Part of the Furniture
Usually, the factory reset won't affect the ability to get to the gui.....I just did an update from 374 with the old http login to 378.55 with the token based login and was able to login fine without a factory reset.

But....if trimming to bare bones with just the single client doesn't work, about the only thing left to try will be to do the factory reset.

If the bare bones does work, he will still need to schedule to do a factory reset as soon as he can.
 

Swiso

Occasional Visitor
Hello guys.
I had to go to work early today, so I will try later this evening the solutions you suggested.
Thanks for the help, really appreciated !

One question....what you mean by "token based login" ?
What's the difference between the classic login Web page ?
 

hank81

Regular Contributor

Txdk

Regular Contributor
You mean turning off and then on again ? Already done this without success.

I tried the port scan with the program you mentioned, it say " port open : 8443, pcsync-https, common alternative https port, pcsync-https, response time 0 (zero).
For the 87U same result, but instead of response time zero (0) i read 2.

when you try to login do you then use https://192.168.1.20:8443 and https://192.168.1.34:8443 or is it standard http://192.168.1.20 and http://192.168.1.34 you use if its http then use https
 

Swiso

Occasional Visitor
When you are running in AP mode, the WAN port is just like the other LAN ports, no difference.

Since you are able to ping the routers, the networking looks good. Unfortunately, we can't get in to look at the syslogs to see what may be happening..but my guess is that the web server is down or not starting correctly.

My next step would be to try this....

Unplug each of your clients (not the powerline/switch interconnects) and then reboot the routers and the netgear switch. Replug you primary client you've been testing from and see if you can get to the gui's then. If you can, immediately go to the Administration > System page and enable telnet and apply (so maybe we can collect additional data later).

Then plug in each client one at a time and retest. As you do this, on the AC87, don't use LAN port 1, it has a special setup and I'd like to eliminate the most variables possible.

There was just another user where having an HP Printer plugged in was apparently causing the router web server to crash (still don't understand that one), so may want to save that one for last.

Ok here I am...
Trying this solution.

By "reboot the routers" you mean ALL THREE ? ( fritzbox :192.168.1.1 , 66U: 192.168.1.20, 87U: 192.168.1.34) and by reboot you mean turning off and then on again ?
thanks
 

john9527

Part of the Furniture
Ahhh....the obvious overlooked :) At some point you must have changed to https logon.....glad to hear it was that easy!
 

john9527

Part of the Furniture

Swiso

Occasional Visitor
S**t...:oops:
Yes...thats embarassing...really ...oh man SORRY to have you bothered for this thing !!
Oh man...

A BIG thank you to everyone for the kind help, especially Txdk to pointing out that tip...
:oops::oops::oops:
 

Swiso

Occasional Visitor

Swiso

Occasional Visitor
Easy? Do you know how much sleep everyone has lost over this one?:)

Well done, Txdk!
Ahaha !! Yeah...I owe evereybody a "virtual" 12-pack of beer to ease the sleepless time !!
Here it is :

Thanks and good night evreybody !
:)
 

cofetym

Regular Contributor
The virtual beer really hit the spot,Thanks Swiso!
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top