I just came here to ask if changing it on the router also changes it on an AiMesh node.. sounds like it doesn't matter. Why is the setting still there?
OK, thanks. It's not something I required.. I just was more curious why it wasn't working. I recall it working on my AC68P at one point, and my new 1900P wasn't working. When I checked the 68P I realized it was the same deal. Thought I was crazy.
Can anyone tell me defnitively whether the AC1900P or AC68P support CTF+FA NAT Accel? I find references to the 68P supporting it.. but they're always older posts. Did Asus remove support for this? I can't seem to enable it. I am up to date on both, running stock firmware (for aimesh, which I...
Can anyone tell me defnitively whether the AC1900P or AC68P support CTF+FA NAT Accel? I find references to the 68P supporting it.. but they're always older posts. Did Asus remove support for this? I can't seem to enable it. I am up to date on both, running stock firmware (for aimesh, which I...
Does anybody know what this means?
Feb 9 06:09:51 kernel: htb: htb qdisc 17: is non-work-conserving?
I'm not getting this a lot in the log but it shows up every few hours. I had never seen it in the prior version of AsusWrt (not the .50 beta).
Has anyone overclocked the AC68P? I have mine currently at 1400 with the temps going between 71 and 73C. Prior to the overclocking it was between 71-72 so no real change.
Try disabling multicast_snooping:
echo "0" > /sys/devices/virtual/net/br-lan/bridge/multicast_snooping
On openWRT you put this in rc.local.. maybe put it in init-start?
This fixed a upnp issue with my Xbox 360 on a client bridge running OpenWRT. I changed the path to be correct for the AC68.