[support]

When you manually set Private DNS on the phone, DNS lookup no longer go through the router. For example, if you set your Private DNS to dns.google, then DNS lookup goes over an encrypted TLS connection to dns.google, bypassing the DNS filter on the router. So it is good that traffic is blocked when Private DNS is used.

However, please note that blocking is effective only when “Block proxy, VPN, TOR” is checked on the profile.

[support]

@prurtz8 The concurrent VPN/non-VPN setup has been fully tested and works well (for both wired and wireless configurations). Please provide more detailed information to us so that we can help you to resolve this problem.

Please send the following to [email protected]:

1. Screenshot of the Network Settings page showing VLAN port assignments
2. Which port is your PC connected to. And a screenshot of the output of the command “ipconfig”
3. A screenshot of the Status page
4. Screenshots of the VPN client pages for OpenVPN, IKEv2 and WireGuard

[support]

@casino When the app was running, everything worked the same as if the app was not used at all. That’s the expected behavior, because it’s a DNS changer.

[support]

VLAN works for wired connections too. Does your phone still have an IP address in the LAN range? Is it getting an IP address via DHCP?

Also, you should connect to the left most port, which is port number 1. I.e., when you look at the back of the router, the port numbers are 1, 2, 3, 4, from left to right.

[support]

IP address for the X1 network should be 10.159.158.x.

[support]

Try rebooting your phone (power off, the power on). Also, login to the router, check the IP address of your phone, should be in the X1 network.

[support]

@casino The host changer app has no effect at all. It just changes the DNS server IP addresses on your phone, plus the option to add your own host name to IP address mappings. This is no different from changing the DNS server IP address on your PC from “Automatic” to 8.8.8.8 (for example). Something else is happening on your phone.

[support]

Is your VoIP phone connected by wire? If so, go to the Network Settings page to create a dedicated VLAN for the phone. I.e., put the port you’re connecting the phone to under a different network name. Reboot the VoIP phone after you do that.

[support]

We have reports of up to 50-feet distance two story house without needing WiFi extenders. For longer distance, the 2.4Ghz channel works better. The number of walls between the router and the device plays a big role. But usually the signal strength is a good indicator (check the Status page, need to be >-80dBm to get decent transmission speed).

Picking the right channel is important if there are a lot of WiFi signals around your house. On the far end, your neighbor’s signal might be stronger than yours. Please check out this post: https://www.pcwrt.com/2017/10/how-to-avoid-bad-wifi-connection-by-changing-the-channel-on-your-router/.

[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

[Author]

Posts