AX3000 - parental controls not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

AX3000 - parental controls not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AX3000 - parental controls not working
AX3000 - parental controls not working
2021-09-07 06:26:10 - last edited 2021-09-08 02:40:04
Model: Archer AX3000  
Hardware Version: V1
Firmware Version: 1.0.9 Build 20200708 rel. 55037(4555)

I have set everything up - and yes i added devices to the profile, and set the system clock, and applied time limits (10pm to 7am).

 

The issue is -  the 'bed time' limits do not stop any device accessing the internet.

 

regards

Richard

  0      
  0      
#1
Options
2 Accepted Solutions
Re:AX3000 - parental controls not working-Solution
2021-09-07 07:56:40 - last edited 2021-09-08 02:40:04

@Jinko 

 

Make sure the Private MAC Address is disabled on your clients, otherwise, the parental control won't take effect.

There's a newer FW release for your device fixing some vulnerabilities.

 

Recommended Solution
  0  
  0  
#2
Options
Re:AX3000 - parental controls not workingwefg-Solution
2021-09-08 02:41:30 - last edited 2021-09-08 02:41:44

@terziyski You are a champion! I upgraded the firmware and ensured private MAC addresses were 'off' on attached devices. That worked. Thankyou very much!

Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:AX3000 - parental controls not working-Solution
2021-09-07 07:56:40 - last edited 2021-09-08 02:40:04

@Jinko 

 

Make sure the Private MAC Address is disabled on your clients, otherwise, the parental control won't take effect.

There's a newer FW release for your device fixing some vulnerabilities.

 

Recommended Solution
  0  
  0  
#2
Options
Re:AX3000 - parental controls not workingwefg-Solution
2021-09-08 02:41:30 - last edited 2021-09-08 02:41:44

@terziyski You are a champion! I upgraded the firmware and ensured private MAC addresses were 'off' on attached devices. That worked. Thankyou very much!

Recommended Solution
  0  
  0  
#3
Options