[support]

We can support it, but we’ll need to add some code to support it. Rough estimate one month or so.

[support]

Leave it on DHCP.

[support]

Just plug it in.

[support]

Looks like it’s supportable. Check back in a week, we’ll let you know.

[support]

WPA3 is currently not supported. It will be added to the WiFi 6 routers (CF-XR10 and AX1800) in the future but so far it’s not a priority because of these reasons:
1. WPA2 still provides adequate WiFi protection given a strong password. The highly reported KRACK vulnerability has been fixed for most devices. Despite the media hype, KRACK is hard to exploit. There were no reported real-life exploits of KRACK.
2. The promised WPA3 security enhancement won’t manifest until all your devices support WPA3. Otherwise you’ll have to run WPA3 with WPA2 compatibility, thus no improvement over WPA2.

Thanks for bring up IP blocking. We’ll look into that. With present functionalities, you can block all literal IP addresses and white list the trusted IP addresses you need. Then you can select a secure DNS filter to block the malicious domains.

You can enter your own block list in the Access Control page, but we haven’t tested it with very big lists (e.g., >10k lines). For routers not listed on our website, you have to compile from the source.

[support]

If your computer is not connected to the LAN network port/SSID, you won’t get access to the router SSH port. Nor can you login the router management page. This is a security feature, so that IoT devices connected to a IoT VLAN or guest devices connected to the Guest WiFi do not have access to the router other than looking at their IP addresses or control ad blocking.

[support]

Update: There was a bug that prevented the WiFi transmission power from being updated for models CF-XR10 and PW-AX1800. This was fixed in v2.6.3. So when you upgrade a CF-XR10 or PW-AX1800 router you’ll get v2.6.3.

[support]

@johnnyjackhammer Thanks for the feedback! What is your hardware model and what firmware version were you upgrading from?

[support]

You’re right.

[support]

Since there are 3 LAN ports, you can assign each port to a different VLAN for 3 wired VLANs. If you need to have more than 3 VLANs for wired connections, you’ll need to add a VLAN aware switch to the router and tag the Ethernet port connected to the switch.

For the VPN router setup, you can use one of the following options to expose the server port:
1. Set the pcWRT router as the DMZ host in your ISP router. Here’s an example for the AT&T router: https://www.pcwrt.com/2017/01/configure-att-nvg510-dmzbridge-to-the-pcwrt/
2. Set up port forwarding on the ISP router for the WireGuard server port. For example, if your WireGuard server runs on UDP port 51820, then set up a port forwarding rule on the ISP router for UDP port 51820.

[support]

You get the LITE features when you install one of the images for TP-Link or Linksys. But you can buy a onetime Premium license to upgrade to the full version for all features. You can find the comparison here: https://shop.pcwrt.com/products/pcwrt-firmware-upgrade

[support]

Can you try rebooting the router? If you could give us some info about how this happened, it will help us find the root cause of this issue and prevent it from happening in the future. Thanks!

[support]

The PW-AX1800 actually displays dBm/mw numbers.

[support]

What is your hardware model?

[support]

LAN and WAN must be different networks, that’s how the router knows it needs to “route” the traffic. You can use the 10.0.x.x range but they must be different networks. For example, you can use 10.0.0.0/24 for one side, 10.0.10.0/24 for the other side.

[Author]

Posts