Asus AIMESH cut out issues, need some help

thewizard1241

Occasional Visitor
Hi everyone,

Been lurking around here but never posted, this forum was exactly what i was looking for. Long story short ive setup AIMESH countless times on different routers, new, used, different models, but have always had the same issue of intermittent cutouts and reconnection after 1 min. The WiFi itself doesn't cut out, howvever the internet cuts out.

I have an Asus DSL-AC68u as the AIMESH Router and an Asus RT-AC68u as the node. Both work flawless as stand alone routers with no issues, hwoever as an AIMESH setup i get cut outs. Not sure whats causing it,

I factory reset them both, rebooted, turned off for a while, changed various settings including changing channels, setting auto channel, turned off universal beamforming, turned off roaming assistant, etc just the usual tricks.

Ive included a log to show what happens everytime it cuts out, any help will be much appreciated thanks!

LOG:

Link goes down V

Jul 7 00:16:06 DSL: Link up -> down
Jul 7 00:16:09 WAN Connection: ISP's DHCP did not function properly.
Jul 7 00:16:10 nat: apply redirect rules
Jul 7 00:16:16 WAN Connection: Ethernet link down.
Jul 7 00:16:36 DSL: Link down -> up
Jul 7 00:16:40 WAN Connection: Ethernet link up.
Jul 7 00:16:40 rc_service: wanduck 12333:notify_rc restart_wan_if 0
Jul 7 00:16:45 nat: apply nat rules (/tmp/nat_rules_vlan3880_vlan3880)
Jul 7 00:16:45 WAN Connection: ISP's DHCP did not function properly.
Jul 7 00:16:46 wan: finish adding multi routes
Jul 7 00:16:46 miniupnpd[12432]: shutting down MiniUPnPd
Jul 7 00:16:46 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Jul 7 00:16:47 miniupnpd[16025]: version 1.9 started
Jul 7 00:16:47 miniupnpd[16025]: HTTP listening on port 60627
Jul 7 00:16:47 miniupnpd[16025]: Listening for NAT-PMP/PCP traffic on port 5351
Jul 7 00:16:48 ddns update: ez-ipupdate: starting...
Jul 7 00:16:48 ddns update: asus_private() interface =vlan3880
Jul 7 00:16:48 ddns update: g_asus_ddns_mode == 2
Jul 7 00:16:48 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Jul 7 00:16:48 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Jul 7 00:16:48 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Jul 7 00:16:48 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Jul 7 00:16:48 dhcp client: bound 5.64.93.173/255.255.252.0 via 5.64.92.1 for 3600 seconds.
Jul 7 00:16:49 ddns update: connected to nwsrv-ns1.asus.com (52.250.42.40) on port 443.
Jul 7 00:16:51 WAN Connection: WAN was restored.

Internet comes back on ^

WIFI LOG:

5G

Interference Level: Acceptable
Mode : AP Only

DFS status: state IDLE time elapsed 0ms radar channel cleared by DFS none

Channel Information
----------------------------------------
Channel 36 A Band
Channel 40 A Band
Channel 44 A Band
Channel 48 A Band
Channel 52 A Band, RADAR Sensitive, Passive
Channel 56 A Band, RADAR Sensitive, Passive
Channel 60 A Band, RADAR Sensitive, Passive
Channel 64 A Band, RADAR Sensitive, Passive
Channel 100 A Band, RADAR Sensitive, Passive
Channel 104 A Band, RADAR Sensitive, Passive
Channel 108 A Band, RADAR Sensitive, Passive
Channel 112 A Band, RADAR Sensitive, Passive
Channel 116 A Band, RADAR Sensitive, Passive
Channel 132 A Band, RADAR Sensitive, Passive
Channel 136 A Band, RADAR Sensitive, Passive
Channel 140 A Band, RADAR Sensitive, Passive
 

OzarkEdge

Part of the Furniture
More like a work around than a solution.

OE
 

OzarkEdge

Part of the Furniture
True, but atleast im getting full duplex interrouting as opposed to half :D
That's not even a work around... that a normal technology difference between a wired and a wireless backhaul. Wired is better unless you need to be mobile.

OE
 

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