I've tested extensively and as many of you will have discovered there are some truly debilitating bugs in the R series routers. Coupled with cnMaestro, these devies are TRULY amazing for supporting customers and managing a large user base. If it weren't for the frustrating bugs... However, there is some hope.
Updated: All tests done on Firmware Version 4.6-R16. I will try to confirm if older issues still exist and update here.
WiFi performance improvements:
Still testing, but these settings improve performance from what I can see. For now I'm not supporting A/B/G and only N or on 5ghz AC/AN. Then settings as follows:
- 2.4ghz on 20mhz channel only.
- Set "Operating Mode" to "Greenfields" on both 2.4ghz and 5ghz. Update: It affects 5ghz as well.
- Turn on A-MSDU on both 2.4ghz and 5ghz.
- Try turning off "TX Burst" in advanced on 2,4ghz.
No sure about 5ghz. Update: It affects 5ghz as well.
Pulling files from a NAS were snappier. Kudos to http://community.cambiumnetworks.com/t5/cnPilot-R-Series-Home-Small/R190V-R190W-Optimal-WiFi-Configuration/m-p/116653/highlight/true#M2085
- Disable "DNS Proxy". Update: If you turn off "DNS Proxy" then turn off "Hardware NAT Enable" if you have WiFi issues in particular WiFi performance.
- Disable "Hardware NAT Enable". Update: Not seeing significant issues with this when this is enabled with "DNS Proxy" turned on.
- Disable "IP conflcit detection". I haven't confirmed if IP conflict detection is working on firmware 4.6 but the others still seemed wonky after some quick tests.
DNS issue workaround:
Turn off the DNS proxy, but there is another issue that's not easy to pick up. If the DNS handed to the router on WAN is the same as the DNS in the DHCP config, when the DNS Proxy is turned off devices will not be able to ping or or lookup the any of those specified DNS servers. To fix you need to add DNS manually on the WAN (any DNS you will never use) and then add your preferred DNS manually assigned on the DHCP server.
Update: Just confirmed the cause of our DNS issues. Disable the "DNS Proxy Enable". Set WAN and LAN to auto DNS – this will assign your customers with the DNS servers you can set upstream via WAN internet interface. Make sure that NONE of your other interfaces (non-routeable) have the same DNS servers specified as your WAN PPPoE / DHCP interface. If they do then the DNS requests may go out of the other interface and because it not routeable, your users won't get DNS lookups or be able to ping the DNS servers. My 1st interface is "Internet" and the second is "Management". A routable interface such as interface type "other" will work with identical DNS server specified, but they will more than likely be going out the "other" interface which could be an issue depending on your network design.
I'm still having issues with the DNS Proxy in 4.6 and will see what combinations may actually function as expected with the various workarounds... Updated: Already mentioned, but "DNS Proxy" on appears fine when "Hardware NAT Enabled" is on.
Interference issue workaround:
If using cnMaestro, run the WiFi Analayzer for the router. You should see any conlficting AP's there. Change the channel manually. Devices such as Roku's will purposefully take the same channel as the R's WiFi. When the R190's experience really bad interference the DNS Proxy seems to turn off. So best turn off the DNS proxy and manually assign the DNS for DHCP as in the DNS workaround above. Update: I haven't been able to replicate the interence and DNS issue with Firmware Version 4.6-R16. It may still be there.
WAN to LAN bridge loop issue:
Watch out when you connect a R series router WAN and LAN (ports) to the same managed switch. The WAN and LAN appear to be bridged, but dissallowed through firewall rules (I'd imagine). What this means is that say you tag your VLAN's on the WAN (PPPoE / Voice etc), untag your LAN on the LAN, IF the VLAN that is tagged on the WAN is also tagged on the LAN (even though the LAN does not have tags) it will cause a LOOP or trigger RSTP.
I hope this helps someone else. I'd really like to see more effort being put into these Routers, as they are essential to tie in all aspects of the ecosystem centered around cnMaestro.
Thoughts and questions welcome.