[support]

Guys, thanks for the feedback! Xbox is broken for now. We’ll fix this and create a new update in the next few days. Sorry, there’s no “rollback” function right now. Maybe we should add that.

[support]

@Sulde Guest network is available since version 1.21. If your version is earlier than 1.20, you need to manually upgrade to v1.20 first. See instructions here: pcWRT firmware v1.20 for TORONTO-N is available for download.

After you upgraded to v1.20, go to the System Settings page, click on “Check for Updates”. You might need to reload the System Settings page (or clean the browser cache) in order for this to work properly.

[support]

@erikrini Currently the router uses ping to check if a device is connected. Xbox does not answer ping, therefore, it’s not listed in the Connected Devices section. This will be fixed in an upcoming update.

In the meanwhile, you can use the Network Settings page to name the Xbox 360. In the “Hostnames and Static Leases” section, click the Add button. In the popup dialog, connected devices should appear under the Name dropdown. You can either identify the Xbox by name or IP address.

Once you identified the device, save the name by clicking OK in the popup dialog. Then click Save at the bottom of the Network Settings page. After that, you can manage the Xbox in the parental control page.

[support]

@Dan As it turned out, Netflix no longer request video streams by literal IP addresses. So blocking literal IP addresses will no longer block Netflix. And, if you want to set up a calendar for Netflix, take a look at this: How to set a calendar on Netflix.

[support]

@RichardGV Thank you so much for bringing this up! I’ve created a separate topic for this, in case someone else run into the same problem.

[support]

@skydogtookmycash We just published the blog post. Any feedback is welcome!

[support]

@mcpheex3 Update v1.21.2 is now available. We think we fixed the STEAM issue. Please check.

[support]

John, Update v1.21.2 is now available. We think we fixed the Status page issue. Please check.

[support]

@geekGirlFri The nohost return code means that dnsomatic cannot find the hostname passed in. Please check your dnsomatic.com page to see if you added the OpenDNS service and that it’s active. If the service is active, there’ll be a green thumb up button on the right of your OpenDNS service row.

FYI, here’s the dnsomatic API reference page: https://dnsomatic.com/wiki/api.

[support]

John, thanks for the update. It turns out that the guest network feature might have introduced a bug in the Status page. We are fixing it now and you can expect an update in the next few days. Thanks!

[support]

John, thank you very much for the feedback! Since there were no changes for the Status page in the last two updates, the page should not be broken (in theory). You are the first one who reported such problems, so please let us know a bit about your network. I.e., how you connect to the Internet and how the devices are connected to the router.

In the meanwhile, you can add new devices in the Network Settings page: in the “Hostnames and Static Leases” section, click the Add button. In the popup dialog, connected devices should appear under the Name dropdown. You can either identify the device by name or IP address.

You can either use tools provided by the OS to identify the IP address of a device (for example on Windows, open a command line window and enter “ipconfig”), or open a browser on the device and enter http://192.168.10.1/myip.html.

Once you identified the device, save the name by clicking OK in the popup dialog. Then click Save at the bottom of the Network Settings page. After that, you can manage the device in the parental control page.

[support]

@MinZhou So the pcWRT router is working as expected. The problem lies in the Internet connection. Do you know what type of Internet connection Comcast provides? Is it DHCP or PPPoE? If it’s the latter, Comcast should have provided you a user name and password to log on. You can get the connection properties from the management console for your old router.

My past experience has been that the connection is DHCP. However, Comcast checks the MAC address on their end. So when you change router, you won’t be able to connect. And that’s why I suggested that you try cloning the MAC address before. I don’t know how you retrieved the MAC address for your old router. You might want to check your old router’s management console. The MAC address might have been cloned there so it doesn’t match what’s on the box.

You may also contact Comcast tech support and ask them for help.

[support]

@MinZhou Because we are testing Internet connectivity, you don’t have to reset the router. Simply change the SSID, or turn off WiFi should work.

But since you’ve reset the router already, you’ll need to go back to the initial setup. You should be able to load the router console with 192.168.10.1.

To keep things simple, disconnect all wires from the pcWRT router. Then connect the power cable only, wait till it’s fully powered up. The SYS and WLAN LEDs should be solid on. Then connect your PC by Ethernet wire to a LAN port on the pcWRT. Load 192.168.10.1 to perform initial setup.

If the above step is successful, connect the pcWRT WAN port to a LAN port on your old router. Again, connect your PC to a LAN port on the pcWRT. Load 192.168.10.1 and look at the Status page. Is Internet up or down?

[support]

@skydogtookmycash Very good questions. Unfortunately there are no clear answers. It might look simple at first glance, but in reality this is a very technical subject. Each family may have different needs and each vendor may approach the problem from a different angle. We are planning to write a blog post to explain some of the factors that have driven our decision making process. Hopefully it’ll help you out somewhat. Stay tuned!

[support]

@abe Thanks for your patience! We are positive that we can work this out. If it turns out that there are bugs in our firmware, we’ll fix them. And yes, you have the right to return if it doesn’t work.

[Author]

Posts