How to Configure Parental Controls on a Verizon Router

Enable an administrator to restrict access to specific hosts from specific machines.

This procedure is intended for use with Verizon’s Actiontec Routers and was tested with firmware version  4.0.16.1.56.0.10.14.4

Model

Model

1. Using a web browser, connect and authenticate to the router.
Result: The router’s main web page appears.

Main

Main

 

2. Click the Parental Control icon from the top bar.
Result: The Parental Control page appears.

Warning

Warning

 

3. Under Step 1, from the left listbox select all the machines which will be blocked. Control or Command click for multiple selections. Click Add.
Result: All of the selected machines appear in right listbox.

Step 1 - Machines

Step 1 – Machines

 

4. Ensure Block the following Websites and Embedded Keywords within a Website radio button is selected. Under Embedded keywords within a Website, enter the hostname to block. Click Add.
Result: The hostname moves to the right listbox.

Step 2 - Rules

Step 2 – Rules

 

5. Next create a schedule. To block 24/7: check Monday through Sunday; Select the Rule will be active at the scheduled time. radio; The start and stop times should be identical.

Step 3 - Schedule

Step 3 – Schedule

 

6. Enter a Rule Name and Description.  The neither should contain special characters. Click Apply.
Result: A confirmation page appears.

Step 4 - Naming

Step 4 – Naming

 

7. At the confirmation page, click apply.
Result: The rule goes into affect.

Step 5 - Confirmation

Step 5 – Confirmation

 

8. Verify rule is in affect.  Key in non-secure http host name into browser.
Result: A blocked message from the Verizon router.

Blocked

Blocked

 

9. Key in secure https host name into browser.
Result: The browser hangs.

 

Here, attempts to connect via ping, ftp, and whois.  All attempts fail.

$ ping ask.fm
PING ask.fm (193.138.77.52) 56(84) bytes of data.

^C
--- ask.fm ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

$ ping 193.138.77.161
PING 193.138.77.161 (193.138.77.161) 56(84) bytes of data.
^C
--- 193.138.77.161 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

$ ftp ask.fm
Trying 193.138.77.53...
ftp: connect to address 193.138.77.53Connection timed out
Trying 193.138.77.52...
ftp: connect to address 193.138.77.52Connection timed out
Trying 193.138.77.161...
ftp: connect to address 193.138.77.161Connection timed out
Trying 193.138.77.157...
ftp: connect to address 193.138.77.157Connection timed out
Trying 193.138.77.158...
^C

$ whois ask.fm
[Querying www.dot.fm]
^C

Some things still work:

$ nslookup ask.fm
Server:         192.168.1.4
Address:        192.168.1.4#53

Non-authoritative answer:
Name:   ask.fm
Address: 193.138.77.53
Name:   ask.fm
Address: 193.138.77.52
Name:   ask.fm
Address: 193.138.77.50
Name:   ask.fm
Address: 193.138.77.51
Name:   ask.fm
Address: 193.138.77.158
Name:   ask.fm
Address: 193.138.77.159
Name:   ask.fm
Address: 193.138.77.157
Name:   ask.fm
Address: 193.138.77.161

 

 

David Gregory Medina

Post created by: David Gregory Medina

Tagged with: , , ,

Leave a Reply