[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.

[support]

I guess that your WiFi was connected consistently but your Internet access has been intermittent? Is that the case?

[support]

Ad blocking on the router is using an internal list, not AdGuard. It’s a combination of multiple lists.

[support]

Agree. Will test this and report back.

[support]

It’s coming soon! We’re testing it now.

[support]

Additional Note: The VLAN ID for the LAN network has been changed to 10 for this release. It was 1 before this release, and it was causing compatibility issues since VLAN ID 1 is reserved in some systems.

[support]

Thermostats and cameras don’t print, so putting the printer in the same IOT VLAN with client isolation won’t hurt them. You want to be able to print from devices connected to LAN and other VLANs such as Guest. Just check the appropriate boxes on the Network Settings page. For example, check all of the boxes corresponding to the IOT VLAN column under the VLAN section. This way, devices connected to VLANs other than the IOT VLAN will be able to initiate communication with devices on the IOT VLAN. But devices on the IOT VLAN can’t initiate communication with other devices, nor can they talk to each other.

You may want to enable mDNS to help your computers find the printer.

[support]

@silviu_25 That was for an older model with a less powerful CPU. The AX1800 has a quad-core 1.2GHz CPU and Access Control does not slow it down.

[support]

Without WG, the max speed is 1000Mbps, with WG the max is 500Mbps. Enforce Access Control does not slow down the speed. Logs are kept in memory with a fixed size. You can look back up to 24 hours, but if there are a lot of Internet activities, it may not have enough memory to keep the full 24 hours.

[Author]

Posts