[support]

The domain wpad.mentorg.com cannot be resolved by Google Public DNS: https://www.nslookup.io/domains/wpad.mentorg.com/dns-records/#google

Also, please check that your firmware version is v2.6.2 or later. There was a bug for ad domains block overriding, which was fixed in v2.6.2. Please let us know if g.live.com still cannot be overridden with the latest firmware.

[support]

@rocket Can you share more info about your script?

[support]

The logs are stored in memory so there is an upper limit to the amount of memory used to store logs. The router admin page allows you to go back 24 hours but the logs may be cut off if you have a lot of Internet activities. Please consider increasing the frequency of backup for your script.

[support]

Currently there are different DHCP pools for different VLANs, except that only LAN is user configurable.

[support]

Let’s say you have two tabs open in your browser, one for site A, another for site B. Both pages contain Google ads. If the router blocks Google ads, then the ads will be blocked for both tabs. The router does not know which tab you’re looking at. That’s why in the current design you need to click a Pause button if you are looking at site A and decided that you want to see ads on the page.

[support]

Can you elaborate on the envisioned user experience? E.g., suppose you go from site A to site B, and from site B to site C. You want ad blocking only for site B. What would you do to achieve that from a user perspective?

[support]

When you activate ad block, it will be enabled for all websites. But you can pause or suspend it before you visit a particular website.

You can perhaps do the reverse. I.e., suspend ad blocking when you log on your computer, but activate ad blocking before you visit a particular website.

[support]

Also, for parental controls, do the “DOH Test” to make sure that your parental controls work: https://www.pcwrt.com/2020/10/does-your-parental-control-pass-the-doh-test/. Make sure sites that are supposed to be blocked are actually blocked.

[support]

We can support it, but we’ll need to add some code to support it. Rough estimate one month or so.

[support]

Leave it on DHCP.

[support]

Just plug it in.

[support]

Looks like it’s supportable. Check back in a week, we’ll let you know.

[support]

WPA3 is currently not supported. It will be added to the WiFi 6 routers (CF-XR10 and AX1800) in the future but so far it’s not a priority because of these reasons:
1. WPA2 still provides adequate WiFi protection given a strong password. The highly reported KRACK vulnerability has been fixed for most devices. Despite the media hype, KRACK is hard to exploit. There were no reported real-life exploits of KRACK.
2. The promised WPA3 security enhancement won’t manifest until all your devices support WPA3. Otherwise you’ll have to run WPA3 with WPA2 compatibility, thus no improvement over WPA2.

Thanks for bring up IP blocking. We’ll look into that. With present functionalities, you can block all literal IP addresses and white list the trusted IP addresses you need. Then you can select a secure DNS filter to block the malicious domains.

You can enter your own block list in the Access Control page, but we haven’t tested it with very big lists (e.g., >10k lines). For routers not listed on our website, you have to compile from the source.

[support]

If your computer is not connected to the LAN network port/SSID, you won’t get access to the router SSH port. Nor can you login the router management page. This is a security feature, so that IoT devices connected to a IoT VLAN or guest devices connected to the Guest WiFi do not have access to the router other than looking at their IP addresses or control ad blocking.

[support]

Update: There was a bug that prevented the WiFi transmission power from being updated for models CF-XR10 and PW-AX1800. This was fixed in v2.6.3. So when you upgrade a CF-XR10 or PW-AX1800 router you’ll get v2.6.3.

[Author]

Posts