@abe Glad to hear it’s working now! Please save a backup now and discard previous backups. You should be able to restore from this backup going forward when there’s a need.
@abe Sorry about your troubles. The MAC address might be the problem. You may try one of the following:
@dadmin To our best knowledge, the pcWRT router is not affected. Per Ars report, there’s no evidence of infection for similar firmware such as Tomato, Merlin and DD-WRT either.
Even though the cause of infection is not clear, the presumption is that it is exploiting known flaws, e.g., unpatched firmware, default passwords, remote admin interface, etc. The pcWRT router does not have a default password, and it doesn’t open a server port on the router for remote admin. If you do enable remote admin for pcWRT, the communication between the router and pcwrt.com is encrypted with TLS. Whereas some major brands does remote admin via plain HTTP.
@abe This is a one time issue – for this upgrade only. You should be able to restore settings as usual after this.
After reset, you’ll do the initial set up again. At this point, you’ll configure the WiFi. Confirm that you have only one SSID after initial setup.
Then you can restore your backup, but choose “Access Control” only. And that should not change your WiFi configuration. Verify again that there’s only one SSID.
Then manually update Dynamic DNS, Cloud and other settings if needed.
Finally, save a new backup.
We should be able to address some of these.
For 2), our thinking is not to make a separate UI element for ports. We have a systematic way of processing Allowed and Blocked URLs. Allowing and blocking ports is just a special case of the whole theme. Please refer to our new blog posting to see how it works: https://www.pcwrt.com/2018/06/how-to-allow-or-block-web-sites-on-the-router/.
@casino The router settings, which apply to all devices, will not make your PC different. Some program and configuration on your PC is making it behave differently. Are you running another parental control program on the PC?
@casino Yes, we managed to see the same error you saw, once. But our experiences on the XP with an outdated version of Chrome were not the same as yours. To be more specific:
Even on our XP PC with the same version of Chrome as yours, the problem can be cleared by flushing the DNS cache (as expected). It’s natural to suspect that there’s something special about your PC. Does “ipconfig /displaydns” come back empty after you run “ipconfig /flushdns“, now that you’ve removed the hosts entries? Are you running any other DNS service on the PC?
@Casino Please understand that this is not a pcWRT bug. We used the same OS and same browser version as yours and cannot reproduce the problem. It’s a problem specific to your PC. And that explains why no one else was complaining.
Can you remove your hosts entries on the PC and see if the problem goes away?
Ok, we got hold of a Windows XP box with Chrome version same as yours. We managed to repeat your error once. But the error went away immediately after we cleared the DNS cache with “ipconfig /flushdns“. We tried to repeat the error for a second time but were not able to.
One thing we noticed was that after we cleared the DNS cache, Windows XP was no longer caching DNS answers. That helps explain why we weren’t able to repeat the error. And it seems to indicate that Windows XP DNS caching is somewhat unpredictable.
After you do “iptables /flushdns“, can you do “iptables /displaydns” to see if the DNS cache was really cleared?
Also, if this happens again, can you reboot the PC instead the router and see if the problem goes away?
@casino Sorry we weren’t able to reproduce your problem. What operating system are you using, and what is the command you use to clear the DNS cache?
You may try this:
If you are able to play the game, then the game does not need an Internet connection to play.
If you are not able to play the game, open the pcWRT management console and check the Internet logs. See what connections were blocked for the PC. Enter the appropriate domains in the Blocked URLs box.
When they do that, a named device becomes an anonymous device, and falls under the control of the Default profile. You need to enable control on the Default profile.
But when you look at the logs, you’d see an unrecognized device. To discourage them from changing the MAC addresses of their devices, you can put the most strict control on the Default profile. And put named devices under more reasonable control.
@casino Since you are the first one reporting this problem, please provide more details so that we can recreate it.
For example, what steps did you take? Did you disable parental control at the router level? What websites were you trying to access and were blocked? What were the settings for the profile to which your device belong? Or does it block devices in all profiles?
@casino That cannot be done at the router. Because the router only knows about the connections between endpoints (devices), it does not know which program (i.e., Vuze or a browser) initiated the connections. For Vuze or eMule to work, you have to disable blocking on “VPN/proxies, TOR” for the device running Vuze or eMule. Alternatively, if those programs support tunneling through VPN or proxy, configure them to use a VPN/proxy, then white list the VPN/proxy endpoints on the router.