[support]

Normal extenders extend one SSID at a time. So you’ll need multiple extenders for multiple networks. But there are dual band extenders that will let you extend one 2.4GHz and one 5GHz. The pcWRT router currently does not support extender mode.

[support]

Sounds like pretty long distance. I’m not sure how much signal degradation there is, but if the signal strength is > -80dBm range, you may get pretty good transmission speeds by trying different channels.

[support]

The range should not be affected. When you create multiple SSIDs, they are basically time-sharing. BTW, what kind of range are we talking about? Are there any concrete walls?

[support]

You don’t need a second pcWRT. A normal extender or repeater would work. Or, you can use a mesh router as AP. Put the mesh router in bridge mode then connect to the pcWRT.

[support]

Update: For TORONTO-AC and Newifi-D2, please update to v2.1.1. Ad block bypassing and DDNS for OpenDNS were broken on v2.1.0.

[support]

It’s actually not blocked. If you’re requesting content from this domain, it’ll succeed (and there will be a record in the Visited tab).

There’s something wrong with the DNS record for this domain. DNS query reports non-existing domain (NXDOMAIN) after the IP addresses are returned. And the last NXDOMAIN record causes the router to add a failed record in the logs.

$ nslookup s.srvsynd.com 1.1.1.1
Server:         1.1.1.1
Address:        1.1.1.1#53

Non-authoritative answer:
Name:   s.srvsynd.com
Address: 18.204.98.216
Name:   s.srvsynd.com
Address: 18.205.232.214
Name:   s.srvsynd.com
Address: 34.231.4.204
Name:   s.srvsynd.com
Address: 34.236.210.83
Name:   s.srvsynd.com
Address: 34.226.87.209
Name:   s.srvsynd.com
Address: 18.204.190.178
Name:   s.srvsynd.com
Address: 35.168.165.225
Name:   s.srvsynd.com
Address: 18.206.31.91
Name:   s.srvsynd.com
Address: 54.156.10.4
Name:   s.srvsynd.com
Address: 52.54.19.1
** server can't find s.srvsynd.com: NXDOMAIN

[support]

We’ll be looking into this. Thanks for your patience!

[support]

You can find instructions from here: https://openwrt.org/toh/tp-link/archer-c7-1750

[support]

@casino By your comment on Feb 10, I thought this was no longer a problem?

[support]

@casino When you block Proxy/VPN, the router automatically blocks literal IP addresses for encrypted traffic. Because the router cannot look inside the encrypted traffic to see if the connection is actually being used as a proxy, it assumes that the connection might be a proxy and blocks it.

[support]

Just FYI. Some of the IP addresses in the IP address range 23.192.0.0/11 are those of CDNs. Blocking this range will break some websites. For example, msn.com.

[support]

@jake This does not sound like normal browser behavior. Does this happen to all your browsers across all platforms?

On the router you can enter the CIDR IP address range as 23.192.0.0/11! in the black list. This is the “force block” syntax. I.e., both direct IP address requests as well as domains resolving to these IP addresses are blocked. More info on the black/white list syntax is available here: https://www.pcwrt.com/2020/01/how-to-allow-or-block-web-sites-on-the-router/.

[support]

@jake Blocking is mostly outbound. Inbound connections are automatically blocked by the firewall, unless the port is specifically opened with port forwarding. Inbound packets are DROPped unless the port is open.

Are you saying that you have open ports on your network and those open ports are constantly scanned by hosts from 23.192.0.0/11?

[support]

This is unfortunate. TOR traffic tunneled through ajax.aspnetcdn.com is indistinguishable from normal HTTPS. If you block it, both will be blocked, if you unblock it, both will be unblocked.

[support]

@casino Thank you! Both 16Mb and 32 Mb are enough for current purposes. There’s no impact on performance.

[Author]

Posts