Hi
My RT-AC88U is running 386.9 firmware since it was published.
Since then I lost internet connectivity a couple of times; the last one I had the change to connect a cable to the internet provider router and checked that it was working fine.
Now I do have internet access, I can ping the router ip address but I cannot access the router either via SSH or HTTPS.
Currently I do not have the router syslog redirected to anywhere.
Any HTTPS connection attempt ends with timeout.
An SSH connection attempt returns the following message:
kex_exchange_identification: Connection closed by remote host
Connection closed by 192.168.131.1 port 22
Found some articles suggests that the message above might be returned if the system running the SSHD daemon suffers some lack of resources.
Any ideas ?
Is there any other recommended firmware level for this router that doesn't cause such type of failures ?
I really need to have the most reliable solution.
Thanks in advance.
PS: I never seen this happen while running some Merlin firmware fork based on 380.70 ... and I ran it during years.
My RT-AC88U is running 386.9 firmware since it was published.
Since then I lost internet connectivity a couple of times; the last one I had the change to connect a cable to the internet provider router and checked that it was working fine.
Now I do have internet access, I can ping the router ip address but I cannot access the router either via SSH or HTTPS.
Currently I do not have the router syslog redirected to anywhere.
Any HTTPS connection attempt ends with timeout.
An SSH connection attempt returns the following message:
kex_exchange_identification: Connection closed by remote host
Connection closed by 192.168.131.1 port 22
Found some articles suggests that the message above might be returned if the system running the SSHD daemon suffers some lack of resources.
Any ideas ?
Is there any other recommended firmware level for this router that doesn't cause such type of failures ?
I really need to have the most reliable solution.
Thanks in advance.
PS: I never seen this happen while running some Merlin firmware fork based on 380.70 ... and I ran it during years.