RT-AC68U Problems

[Vipermk2]

Not sure if I'm posting this in the correct place but I have been having problems with loss of connection and being locked out of my AC68U with all firmware since 3004.378.4585. This is the version which I am using now and is the lastest stable build. Normally it runs fine for about 4 or 5 days and the only time I notice is when I lose internet connection on all wired or wireless devices. I try log into the Router via harwired connection but it just come back with connection problem, I have to reboot to gain access to the web interface. With each new release of the Official Fimware I upgrade in the hope the problem has been resolved but unfortunately the problem remains. The lastest version nearly lasted 2 days before I lost connection, each time I upgrade the firmware I do a factory default then reload my settings. I have the logs from the most recent firmware upgrade (character count allowing) leading up to the last lockout. Would it be worth trying Merlin's Firmware.

It was working at 01.30 but when I got up this morning it wasnt

Jan 31 16:14:43 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.2:2869): Connection timed out
Jan 31 16:14:43 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.2:2869): Connection timed out
Jan 31 18:32:21 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 18:32:27 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.5:2869): No route to host
Jan 31 19:15:41 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 19:21:33 miniupnpd[790]: upnp_event_recv: recv(): Connection timed out
Jan 31 19:41:38 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 19:44:59 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.244:2869): No route to host
Jan 31 19:48:29 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 20:37:44 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 21:00:46 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 21:24:28 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 21:24:31 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Jan 31 21:24:32 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.244:2869): No route to host
Jan 31 23:00:28 disk_monitor: Got SIGALRM...
Feb  1 06:07:39 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 06:15:23 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.5:2869): No route to host
Feb  1 07:36:44 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 07:36:45 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 08:09:32 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 08:21:17 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.5:2869): No route to host
Feb  1 16:57:42 miniupnpd[790]: HTTP Connection from 192.168.1.244 closed unexpectedly
Feb  1 16:57:42 miniupnpd[790]: HTTP Connection from 192.168.1.244 closed unexpectedly
Feb  1 16:57:43 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 17:08:35 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 17:29:07 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 17:29:09 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 17:51:03 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 18:09:30 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.5:2869): No route to host
Feb  1 19:58:41 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 20:26:35 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  1 20:26:48 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.244:2869): No route to host
Feb  2 06:03:09 miniupnpd[790]: upnp_event_recv: recv(): Connection reset by peer
Feb  2 06:21:49 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.5:2869): Connection timed out
Feb  2 06:21:49 miniupnpd[790]: upnp_event_process_notify: connect(192.168.1.5:2869): Connection timed out
Feb  2 06:45:03 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:03 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:03 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:03 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:04 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:04 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:15 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:15 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:16 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:17 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:17 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 06:45:17 miniupnpd[790]: Unknown udp packet received from 192.168.1.2:1900
Feb  2 07:26:16 miniupnpd[790]: HTTP Connection from 192.168.1.2 closed unexpectedly

 

[wardog]

Do you REALLY need UPnP enabled?

Or even look in your modem logs for errors connecting upstream to your ISP !!

Is 192.168.1.244 a device(IP) outside of your available IP Pool?

 

[Vipermk2]

Do you REALLY need UPnP enabled?

Or even look in your modem logs for errors connecting upstream to your ISP !!

Is 192.168.1.244 a device(IP) outside of your available IP Pool?

Thanks for the reply, I did intially set up UPnP for P2P but have forwared the ports for the client so have no need for it now and have disabled it.

I've not looked into how the modem behaves, it's a BT modem and will have to google how to do it but it only seems to be a problem when I use firmware after version 378.4585. I would stay on this but the RT-N66U repeater wanders round the IP range which leads on to your other point the IP pool has now been reduced to 30. The later firmware seems to keep my Repeater to the allocated IP and I also like the ability to assign images to the connected devices. I'm trying the lastest Merlin version to see if it become s more stable, I dont seem the get the 2.4 dropout like other are having trouble with so I'll just see how it goes.

 

[Yiannis]

I have also faced similar problems. Some times , not very often though, it looses WAN connection every 10-15 minutes.
I believe the problem is related to the RT-AC68U rather than the modem side. Last time it happened I was using utorrent. Don't know if this makes any sense to somebody else.

Overall I'm very happy with the ASUS router and its features.

 

[joegreat]

I believe the problem is related to the RT-AC68U rather than the modem side. Last time it happened I was using utorrent. Don't know if this makes any sense to somebody else.

Reminds me about my ISP: If I rund torrenting with >200 connections the WAN side is down and needs a modem reboot to come up again!
The ISPs are shaping their network traffic and do not want people to seed via their network!!!

So it might not be your good old router but your ISP who is blocking you!

 

[zoid009]

Hi!
How did you solved this problem? Clients DHCP tries to renew the address.

Oct  9 13:31:48 miniupnpd[14644]: upnp_event_recv: recv(): Connection reset by peer
Oct  9 13:32:32 dnsmasq-dhcp[2770]: DHCPREQUEST(br0) 192.168.1.14 00:90:f5:49:de:bd
Oct  9 13:32:32 dnsmasq-dhcp[2770]: DHCPACK(br0) 192.168.1.14 00:90:f5:49:de:bd
Oct  9 13:32:35 miniupnpd[14644]: upnp_event_recv: recv(): Connection reset by peer
Oct  9 13:47:59 miniupnpd[14644]: remove port mapping 29136 TCP because it has expired
Oct  9 13:47:59 miniupnpd[14644]: remove port mapping 29136 UDP because it has expired

 

[sanke1]

@Vipermk2

Exact same problem. I have reverted all my 3 RT-AC68Us to 3.0.0.4.380_1842

That is the last flawless version which just works. All the subsequent firmwares cause my LAN and WiFi clients to loose internet connectivity and any webpage gets redirected to router home page router.asus.com

Maybe this is a planned obsolescence strategy to get us to upgrade to their piece of shiii newer routers.

 

[zoid009]

9 Oct the updated router-Merlin 380.62_1 the problem became less but still looking. In the magazine there are 4 errors.

Oct 10 00:08:08 miniupnpd[593]: upnp_event_recv: recv(): Connection reset by peer
Oct 10 10:07:06 miniupnpd[593]: upnp_event_recv: recv(): Connection reset by peer
Oct 10 10:07:07 miniupnpd[593]: upnp_event_recv: recv(): Connection reset by peer
Oct 11 17:12:50 miniupnpd[593]: upnp_event_recv: recv(): Connection reset by peer