Forums

Home Forums Announcements pcWRT firmware v2.0.5 Release Notes

pcWRT firmware v2.0.5 Release Notes

This topic contains 7 replies, has 4 voices, and was last updated by  support 20 hours, 33 minutes ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #3406

    support
    Participant

    Changes included in this update (v2.0.5):

    • Allow remote control for the router when it’s behind another router/NAT
    • Add protection against DNS rebinding attack to Network Security section
    • Add forced IP address blocking syntax for black list: 192.168.100.1! With forced IP address block, black list not only blocks access when the IP address is used, but also when a domain name is used and that domain name resolves to the blocked IP address.
    • Change Access Control regular expression syntax to be POSIX extended
    • Bugfix for missing escape character ‘\’ in regular expression black/white lists
    • Fixed bug that broke local network IP address change
    • Fixed bug that broke port forwarding with Access Control enabled in some scenarios
    • other minor bug fixes

    Upgrade steps:

    1. Have your configuration backup ready. Create a backup of your current configuration file, if you don’t have one.
    2. Click the “Check for Updates” button in the System Settings page. Follow the instructions to upgrade.
    3. After successful upgrade, create a new router settings backup file from the System Settings page and save it in a safe place.

    Important Note for TORONTO-N: If you are upgrading from a version earlier than v1.26, your current configuration might be wiped out during this upgrade because of the WiFi driver upgrade. If you use the “Restore Backup” button in the System Settings page to restore from an earlier backup, please restore only Access Control settings. You need to manually enter other settings after restoring Access Control.

    #3411

    Casino
    Participant

    Can you give of us an example about the point 3? “Add force IP etc… thanks.

    #3412

    knoxploration
    Participant

    Allow remote control for the router when it’s behind another router/NAT

    Tested and working nicely. Shame you can’t check / upgrade firmware remotely though, as that’s basically the only reason I ever log into the thing in the first place once it’s configured, so I still have to change to its Wi-Fi network first.

    Oh, and by the way, you have a minor display bug in the router selection page for remote control. Although you can include characters like ‘ in the router display name — and indeed, your guide at https://www.pcwrt.com/forums/topic/how-to-remote-control-the-pcwrt-router/ does so — when you are shown the list of routers to select from, you see the escaping in the display (eg. “Kids\’ Router” instead of “Kids’ Router”).

    #3417

    support
    Participant

    @casino Let’s assume that www.my-cable-modem.net resolves to IP address 192.168.100.1. If you put 192.168.100.1 in the black list, then http://192.168.100.1 is blocked. However, http://www.my-cable-modem.net is not blocked. That’s the way it should work because multiple web sites may be hosted on the same IP address and you only want to block the domains listed in the black list.

    There may be occasions you want to block an IP address, no matter what name is used to access it. That’s when you want to use the forced block syntax: “192.168.100.1!”. When an exclamation mark is appended to the end of the IP address, all domains that resolve to the IP address are also blocked (e.g., www.my-cable-modem.net).

    #3418

    Casino
    Participant

    Thanks for the explanation.

    #3419

    support
    Participant

    @knoxploration Thanks for the feedback. The display bug had been fixed. The problem with remotely upgrading firmware is, you don’t have any options to recover if something goes wrong. As a precautionary measure we don’t support remote upgrade.

    #3477

    aaronwilliams
    Participant

    “Allow remote control for the router when it’s behind another router/NAT”

    that feature has worked for me for ages now. what’s different in 2.05? i think to get it working i had to port forward it through the first router. is this new feature supposed to eliminate the need to port forward in the WAN facing router?

    #3478

    support
    Participant

    @aaronwilliams You’re right. Port forwarding no longer needed.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.