1/4
How to block YouTube and Facebook on specific VLANs or IP addresses?

xonivre Lv1  Posted 2026-Sep-17 13:14

Hi all

I am using a Sangfor NSF-1100A-I running firmware version 8.0.95.

I would like to know the recommended and most reliable way to block YouTube and Facebook for users on specific VLANs or IP addresses.

My requirements are:

Block YouTube and Facebook completely for selected users/VLANs.
Allow YouTube and Facebook only for specific registered IP addresses.
Prevent users from bypassing the restriction by using HTTPS, mobile applications, or alternative domains.
If possible, automatically block or enforce the restriction using Application Control, URL Filtering, or another built-in security feature.
I would also like to know if there are any limitations or known issues with YouTube/Facebook blocking on firmware 8.0.95.

Could you please provide the exact configuration steps for firmware 8.0.95 and recommend which feature should be used?

Thank you.

rizzuan has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Hi,

For this requirement, I would recommend using an Access Control policy combined with URL Filter and Application Control rather than relying on URL filtering alone.

Suggested approach:

Create Network Objects for the allowed IPs/VLANs and the restricted VLAN/subnet.
Create an Application Control policy for YouTube and Facebook, with the restricted VLAN/subnet as the source.
Create a URL Filter policy using the relevant URL categories or a custom URL category for YouTube/Facebook domains.
Set the action to Deny/Block for the restricted source.
Place the allow policy for registered/approved IPs above the blocking policy, so the approved users are exempted.
Enable logging and verify the matched policy from Access/Application logs.

One important point is that YouTube and Facebook use multiple domains and HTTPS traffic, so URL filtering alone may not always provide complete application blocking. If traffic needs to be controlled more strictly, Application Control and, where applicable, HTTPS/SSL inspection should also be considered.

For the exact behaviour on firmware 8.0.95, I would also recommend checking the Application Control/URL Filter logs after applying the policy to confirm which signatures and domains are actually being matched
Is this answer helpful?
xonivre Lv1  Posted 2026-Sep-21 09:36
  
Thank you so much! This is a big help. I really appreciate the detailed explanation and guidance. I’ll try setting it up this way and check if the issue persists.
Humayun Ahmed Lv4  Posted 2026-Sep-17 14:16
  
              INTERNET
                  │
                  ▼
        ┌───────────────────┐
        │ Sangfor NSF-1100A │
        │     8.0.95        │
        └─────────┬─────────┘
                  │
        ┌─────────┴──────────┐
        │                    │
   Approved IPs        Restricted VLAN
        │                    │
        ▼                    ▼
  ALLOW YouTube/FB      DENY YouTube/FB
                              │
                              ▼
                    URL Filter / HTTPS
                              │
                              ▼
                    VPN/Proxy Control
youssef Lv1  Posted 2026-Sep-17 13:51
  
Hi,

Here's the recommended approach:

URL Filtering — configuration steps:

Object > Content Identification Database > URL Category — add a self-defined URL category with your domains (youtube.com, facebook.com).
Objects > Security Policy Template > Content Security — create a new template, select your custom category under URL Filtering.
Policy > Network Security > Policies — create a policy: LAN zone/subnet as source, WAN zone as destination, apply the Content Security template from step 2.

Precautions:

Single-arm/mirror mode does not support URL filtering — interface must be route or bridge mode.
Filtering works via domain checking (HTTP Host header / HTTPS SNI field), so it catches HTTPS without needing full decryption — but only at domain level.
Keep the URL database updated for best accuracy.

For your allow-list requirement:
Create a separate policy scoped to your registered IPs, placed above the block policy in the policy order, with the same URL category set to Allow.

For app-based bypass (mobile apps, non-browser traffic):
Layer Application Control alongside URL Filtering — it matches on app signatures rather than domain, catching cases plain URL filtering misses.

If bypass persists after this setup, I'd recommend opening a support ticket to check against known issues for your firmware build.

Hope this helps!
Prosi Lv4  Posted 2026-Sep-17 13:33
  
Hi,
Sangfor's official documentation for Athena NGFW 8.0.95 confirms that both URL Filter and Application Control are available in this version. The documentation also indicates that HTTPS filtering requires the HTTPS option to be enabled for URL/content filtering to operate on HTTPS traffic.

I Can Help:

Change

Moderator on This Board

1
160
3

Started Topics

Followers

Follow

1190
263
101

Started Topics

Followers

Follow

Board Leaders