[support]

@rjager Logging does not exist at this point. This is being worked on currently and is expected to be available 1Q next year. The current workaround is to use OpenDNS Home logging reports, which is viewable on OpenDNS website. The OpenDNS report is for your home network as a whole. But you can configure pcWRT so that parents use a different DNS provider, effectively making OpenDNS report on all kids devices.

[support]

@rjager You don’t need to wait for our new hardware. The current 300 Mbps TORONTO-N model will satisfy your needs. Here’s our suggestion:

1. Connect the devices like this:
   Airplay Express -> pcWRT router -> Internet (modem).
   I.e., connect the Airplay Express WAN port to a LAN port on the pcWRT, then connect the pcWRT WAN port to the modem.
2. Turn off WiFi on the pcWRT (do that in the Wireless Settings page).
3. Configure the Airplay Express as an Access Point by following the steps outlined here: http://www.all4you-sprl.be/configuring-an-apple-airport-express-as-an-access-point-of-an-existing-network/

With this setup, all your devices still connect to the Airport Express. But you can apply parental controls to the devices via the pcWRT router. You should be able to see these devices when you log on to the pcWRT management console.

[support]

@jgindin Thanks for the suggestions. The new hardware will have features that are currently available. But we’ll add new features as we have the resources to do so. Site monitoring is the next priority that we’ll be working on.

“Block proxy, VPN, TOR” actually blocks the protocols. Blocking access to anonymizing sites can be accomplished by OpenDNS.

Guest network function is available now. The demo is not up-to-date on that. Parental control works the same for the same device, either through the guest network or the main network. However the two networks are separated, i.e., devices connected to the guest network cannot talk to devices connected to the main network.

[support]

@porkchop The DC input for TORONTO-N is 5V 1A.

[support]

@skydogtookmycash The new hardware will be about the same as the C7, though the combined WiFi throughput is lower. The advantage for the C7 is it’s established hardware. The advantage for the new hardware is that we have more control. But we will continue to support the C7 with updates nonetheless.

The pcWRT router has been successfully used with WiFi extenders by many users. So far we haven’t heard any report of incompatibilities.

@jgindin We’ll try our best to make it available before the end of the year. It definitely will be available 1Q next year.

[support]

Hmm, this does not normally happen. To help us understand the problem, can you provide some more details?

1. You only configured the Wifi parameters and Internet, no other configuration was changed from default. Right?
2. What’s your Internet speed by the ISP?
3. How often does this happen? Does it happen periodically or at random times?
4. When you lose Internet connection, is it Wifi only or is wired connections to the router also dropped?
5. What’s the error if you try to load a web site in the browser?

[support]

@Transversal The new hardware will be a dual band AC router with 1200Mbps combined WiFi throughput. It will be less expensive than the Archer C7. We’ll enter the testing stage soon, which will determine when we can make this available. While we want to get it out of the door ASAP, we also want to make sure that we don’t release it prematurely. Thanks!

[support]

You can perform these two tests to start with:
1. Wired vs. wireless: compare the speed connecting to the pcWRT router by wire with the speed by WiFi.
2. If there’s no difference above, then connect a device directly to the modem (or ISP provided router) by wire. Compare with the speed in step 1.

[support]

@MicheleSmith Thanks for contacting us. Using the forums here is the preferred way to get help. Since any problems and solutions shared here might also be helpful to other people. If there are any privacy concerns, you can contact us via email: [email protected].

I suppose that your connection is like this:

pcWRT router -> Time Warner router -> Internet.

Did you have WiFi enabled on both the pcWRT router and the Time Warner router? If so, your computers and devices can connect to either the pcWRT or the Time Warner. Only the devices connected to the pcWRT can be controlled. If a device is connected to the Time Warner router, it goes to the Time Warner directly and out to the Internet without passing through the pcWRT. I.e., the pcWRT router does not have a chance to control anything.

There are two ways to solve this problem (you can pick either one, though option 1 is preferred):
1. Disable WiFi on the Time Warner.
2. Only give the pcWRT WiFi password to kids, keep the Time Warner password secret.

Does this answer your question?

[support]

@mizarcs Please check that you disabled the options “Block literal IP addresses” and “Block proxy, VPN, TOR” for the profile that the phone belongs to.

[support]

In theory turning parental control off on a profile should behave the same as when parental control is completely off on the router (for devices in the profile). You can try a simple test scenario first:
1. Enable parental control for router.
2. Delete all profiles except Default (which cannot be deleted).
3. Disable parental control for the Default profile.
4. Select System Default for DNS Servers.
5. Save the changes.
6. Test with the Nintendo 2DS and see if the problem persists.

[support]

@Max You can do a test. Make a backup of your current configuration if you haven’t already.

Make sure parental control is enabled. Then unplug the power. Power up the router again. Login to check the status of parental control. Is there any change?

If parental control is disabled after rebooting, reset the router. Then do the initial setup. Then restore your backup. After restoration, repeat the test. Configuration should not change after rebooting.

BTW, what is the firmware version?

[support]

For parental controls to work, the device must use the router’s DNS service. When DNS requests go through the router, the router forces the controlled device to use the DNS services set up in the router. But for devices that are authenticated by your DC, you must give the DC the first chance for DNS resolution, because the router doesn’t have any knowledge of the domain configuration.

If you configure your browser to use the authenticating proxy, then all traffic initiated from the browser will use the DNS service provided by the proxy. This may be different from the DNS service used by the system, i.e., when you authenticate at login.

[support]

When a device connects to the router, DNS setting is pushed out to it. The router can push its own IP address, or that of the DC. It can’t send one for some devices, and the other for other devices.

[support]

That doesn’t work. You still want the devices under parental control to use the DNS provided by the router.

[Author]

Posts