[support]

If you connect the Hubitat hub to a port assigned to X1, then all devices connected to the Hubitat will be on the router’s X1 network.

[support]

Please refer to this post on how to set up the router as an Access Point: https://portal.pcwrt.com/blog/2024/12/how-to-set-up-a-second-pcwrt-router-as-an-access-point-with-vlan-support/

[support]

Please refer to this post: https://portal.pcwrt.com/blog/2024/12/how-to-set-up-a-second-pcwrt-router-as-an-access-point-with-vlan-support/.

[support]

The three choices for AdGuard are:

• Default: Blocks ads, trackers, malware, and phishing websites
• Family protection: Blocks ads, trackers, malware, phishing websites, and adult content
• Non-filtering: Provides a secure connection without blocking anything

The IP addresses 94.140.14.14 and 94.140.15.15 are AdGuard Default, which include ad blocking. If you choose this option and enable “Ad Blocking” in Access Control, then ad blocking will be the union of both lists.

Ad blocking via the Access Control option can be bypassed on demand by clicking the Pause button on the Ad Block Control page. But it doesn’t bypass ad blocking via AdGuard DNS.

[support]

That’s not the message from the router blocking ping across VLANs. The latter looks like: “From 10.159.157.1 icmp_seq=1 Destination Port Unreachable”.

How are the devices connected on the X1 and LAN networks? Does the destination host block ping?

[support]

If you checked the box on row LAN and column X1, the you should be able to ping a device on X1 from a device on LAN. Vice versa for X1 and LAN.

“Block Ping” is for ping blocking from the WAN.

What response did you get when you ping LAN from X1?

[support]

@bh333 Please send a copy of your backup to [email protected] so that we can investigate this issue.

[support]

If you set device isolation on “LAN”, devices connected to LAN can still access the router. But they can’t talk to each other.

[support]

@bh333 This might be a backup compatibility issue. To test it, you can create a fresh backup and try to restore it immediately. It you get the same error, there may be other issues.

You might still restore the access control portion if there is a backup compatibility issue.

[support]

@just_a_goat2 That’s a good suggestion! We’ll see if it can be done.

As a workaround, you can configure the IoT VLAN to go through a VPN but don’t actually create the VPN connection. That’ll effectively block any outbound traffic from IoT.

[support]

Yeah you can create a 2.4GHz SSID with X1 for IoT. If you connect your laptop to LAN and IoT on X1, then you need to enable LAN to X1 communications (i.e., check the box with source LAN and destination X1, which is on by default).

You can use Access Control to block Internet access for devices. Just create a profile with “White List” URL filtering but enter no domains in the white list box.

[support]

When you click the “Check for Updates” button, you’ll have the option to rollback to the previous release if you are on the latest release.

[support]

We’ll add a blog post to explain this soon.

[support]

@koningskruid Thanks for reporting this. The bug has been fixed and released. The latest version number has been bumped up to v2.7.6.

[support]

We just put in a fix to the bug where disabled WiFis were activated without password during upgrade. The version number has been bumped to v2.7.6.

[Author]

Posts