RT-N66U - problem with wired clients and wan dropping

[plex]

Hi

My RT-N66U is getting old, but it has always been very stable - I'm very satisfied with the product value.

But recently the router started to cause trouble... About every other day, no clients can access wan, and all wired clients are missing in the client status window. It means that wireless clients can still access the local network, but only the wireless, as the wired are missing. Well the port led's are still illuminated and flashing...

Internet status remains "connected", and the router has the static ip allocated just fine - but I can't access the internet...

Only solution is to reboot the router.

I've tried the reset the router, since this started, but no effect whatsoever.

I've made two changes since this started.

1)
I've upgraded to 3.0.0.4.376_3754

2)
Moved one wired client, to another place in the house, and installed new cat5e cable.

Can it be the new firmware from Asus - has anyone else occurred problems with the new release?

Router can be faulty?

My new installed cable could somehow mess up everything?

Any help are appreciated

 

[plex]

This is from the log:

Feb 6 21:15:58 ntp: start NTP update
Feb 6 21:16:58 ntp: start NTP update
Feb 6 21:17:58 ntp: start NTP update
Feb 6 21:18:58 ntp: start NTP update

This messages occurs all night, until...

Feb 7 05:50:59 rc_service: httpd 361:notify_rc reboot
Feb 7 05:50:59 ntp: start NTP update
Feb 7 05:51:01 kernel: Attempt to kill tasklet from interrupt
Feb 7 05:51:01 FTP Server: daemon is stoped
Feb 7 05:51:01 Samba Server: smb daemon is stoped
Feb 7 05:51:01 WEBDAV Server: daemon is stoped
Feb 7 05:51:01 WAN Connection: ISP's DHCP did not function properly.
Feb 7 05:51:01 stop_nat_rules: apply the redirect_rules!
Feb 7 05:51:43 rc_service: ntp 464:notify_rc restart_upnp
Feb 7 05:51:43 rc_service: ntp 464:notify_rc restart_diskmon
Feb 7 05:51:43 rc_service: waitting "restart_upnp" via ntp ...
Feb 7 05:51:44 dhcp client: bound 83.92.73.252 via 83.92.73.1 during 253707 seconds.
Feb 7 05:51:44 disk monitor: be idle
Feb 7 05:52:27 crond[363]: time disparity of 2157472 minutes detected
Feb 7 05:53:50 rc_service: httpd 361:notify_rc start_webs_update
Feb 7 05:59:57 ntp: start NTP update
Feb 7 06:59:57 ntp: start NTP update

 

[plex]

Oops - I think I've found the answer.

My newly installed cat5 cable, was miswired (-tx and +tx).

Let's see - so far stable 24 hours after fix