Router slowing down, RT-AC66U newest merlin firmware

[web-ninja]

I am wondering if Cox is messing up or my router is? I am on the latest Merin firmware and I don't see anything that could be causing the drastic slowdown. There are at most 30 wireless devices connected to the router would that be part of the issue? and here is the log about Cox.

Feb 17 17:58:20 miniupnpd[581]: HTTP Connection from 192.168.212.222 closed unexpectedly
Feb 17 18:12:06 kernel: eth1: received packet with own address as source address
Feb 17 18:12:07 dnsmasq-dhcp[541]: Ignoring domain Hamby.local for DHCP host name Tammi-PC
Feb 17 20:04:13 rc_service: httpd 364:notify_rc restart_time;restart_httpd;restart_upnp
Feb 17 20:04:13 kernel: klogd: exiting
Feb 17 20:04:13 syslogd exiting
Feb 17 20:04:13 syslogd started: BusyBox v1.20.2
Feb 17 20:04:13 syslog: Password for 'admin' changed
Feb 17 20:04:13 kernel: klogd started: BusyBox v1.20.2 (2015-02-06 20:45:04 EST)
Feb 17 20:04:13 RT-AC66U: start httpd
Feb 17 20:04:13 RT-AC66U: start httpd - SSL
Feb 17 20:04:13 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Feb 17 20:04:13 dnsmasq[541]: exiting on receipt of SIGTERM
Feb 17 20:04:13 dnsmasq[3887]: started, version 2.73test6 cachesize 1500
Feb 17 20:04:13 dnsmasq[3887]: warning: interface ppp1* does not currently exist
Feb 17 20:04:13 dnsmasq[3887]: asynchronous logging enabled, queue limit is 5 messages
Feb 17 20:04:13 dnsmasq-dhcp[3887]: DHCP, IP range 192.168.212.3 -- 192.168.212.254, lease time 1d
Feb 17 20:04:13 dnsmasq[3887]: using local addresses only for domain HAMBY
Feb 17 20:04:13 dnsmasq[3887]: read /etc/hosts - 5 addresses
Feb 17 20:04:13 dnsmasq[3887]: read /etc/hosts.dnsmasq - 0 addresses
Feb 17 20:04:13 dnsmasq-dhcp[3887]: read /etc/ethers - 6 addresses
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.28.11#53 for domain local
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.28.11#53 for domain ks.cox.net
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.29.12#53 for domain local
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.29.12#53 for domain ks.cox.net
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.28.12#53 for domain local
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.28.12#53 for domain ks.cox.net
Feb 17 20:04:13 dnsmasq[3887]: using local addresses only for domain HAMBY
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.28.12#53
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.29.12#53
Feb 17 20:04:13 dnsmasq[3887]: using nameserver 68.105.28.11#53
Feb 17 20:04:13 RT-AC66U: start httpd
Feb 17 20:04:14 RT-AC66U: start httpd - SSL
Feb 17 20:04:14 miniupnpd[3906]: HTTP listening on port 55993
Feb 17 20:04:14 miniupnpd[3906]: Listening for NAT-PMP/PCP traffic on port 5351
Feb 17 20:08:21 login[3930]: root login on 'pts/0'

 

[jegesq]

Why do you have your private IP range set to "192.168.212.xxx"? And why do you have your DHCP server set to a private domain?

My suggestion would be to do a complete factory reset, and start over by NOT entering any private domain info, and let the Asus just assign the stock "192.168.1.xxx" range of IP's.

Otherwise, I don't see anything particularly odd about your log. Maybe someone else will see something I'm overlooking.

If the nameservers that Cox is providing are having issues, you can always change to another, e.g., something like OpenDNS, Level3, or Google's DNS servers, until Cox manages to get their's back under control.

In the WAN page in the GUI, you will see a small radio button with the label "Connect to DNS Server automatically". Select "No" and then type in the info for the alternate DNS you want to use (e.g., Google is 8.8.8.8 and 8.8.4.4). Give that a try and see what happens.

 

[web-ninja]

"Why do you have your private IP range set to "192.168.212.xxx"? And why do you have your DHCP server set to a private domain? "

The 3rd octet, 212 was set from the previous router, and the server is set at 212.5 that runs a program that is dependent on the particular IP set. trust me I would love to set it to factory. AND dealing with their tech support is a PITA.. I am also working on finding out why they have that local domain? is it even necessary. lol I have the old router right now trying to pick apart the config file and settings.

 

[jegesq]

"Why do you have your private IP range set to "192.168.212.xxx"? And why do you have your DHCP server set to a private domain? "

The 3rd octet, 212 was set from the previous router, and the server is set at 212.5 that runs a program that is dependent on the particular IP set. trust me I would love to set it to factory. AND dealing with their tech support is a PITA.. I am also working on finding out why they have that local domain? is it even necessary. lol I have the old router right now trying to pick apart the config file and settings.

Not sure how you have your DHCP set up. Are you saying that you're getting a private domain setting for DHCP from your ISP? Who is your ISP and where are you located (as in what country)? Whose domain is "HAMBY"? Your private network domain, or??? Whose computer is "Tammi-PC? Is that your's or ??? Why are you relying or using settings from a config file from some previous router? And how are those settings from that prior configuration getting loaded into your Asus AC66U's GUI settings? And what server are you referring to, your ISP, or some other server on your own private LAN?

 

[web-ninja]

This is a private domain coming from their DC. I cleared the dhcp problema nd it is now using the local addresses for the domain it was configured for which is Hamby.local. I am in the USA and COX is the ISP. I manually setup the router with the previous settings. they have programs that rely on those specific IP ranges and ports. What i do not get is I was just looking at the logs and the router either kicked me out, rebooted or just stopped connection? this was at 3:30 AM in the morning. I now do not have access to the routeror able to teamveiw into the server. wierd!

 

[jegesq]

This is a private domain coming from their DC. I cleared the dhcp problema nd it is now using the local addresses for the domain it was configured for which is Hamby.local. I am in the USA and COX is the ISP. I manually setup the router with the previous settings. they have programs that rely on those specific IP ranges and ports. What i do not get is I was just looking at the logs and the router either kicked me out, rebooted or just stopped connection? this was at 3:30 AM in the morning. I now do not have access to the routeror able to teamveiw into the server. wierd!

Let me see if I understand your set up: You have a local domain, so I'm guessing you're running your own server identified as "Hamby" domain. Correct? If so, what device/server is handling your DHCP and routing? Is it your server or your AC66U? And what sort of device are you using to connect to Cox's cable internet service? A simple cable modem that isn't doing DHCP and NAT? Or are you using a cable modem/wireless router gateway device that is also handling DHCP and NATing?

If it's the latter, you should turn off DHCP, put it into "Bridge" mode and turn off NAT and firewall also so that all of that can be handled by your AC66U. Alternatively, if your server is doing the DHCP and NAT duties, then set up your AC66U as an AP, not as a router.