Excluding traffic from inside of your organization


Example

The private networks inside of your organization use the fe80::a00:0 and fe80::c0a8:0 blocks of the IP address space. You need to exclude traffic originating these networks.

To perform this procedure, you must have Operator-level access, or higher.

  1. In the Real User Collector, point to Administration > Data flow settings and click Traffic inclusion/exclusion policies.
  2. On the Action menu for the Client IP include/exclude section, click Add.
  3. Assuming there are no other rules, in the Priority list, use the Append option.

    Note

    If there were other rules, you could click a number corresponding to the priority you want this rule to have, or keep the Append value to add this rule to the end of the policy (followed only by the "catch-all" rule All others).

  4. In the Name box, type Private network 10.
  5. In the IP box, type fe80::a00:0.

    Note

    To learn what client IP addresses and ranges has the system already detected, click lookup to the right of the IP box.

  6. Do one of the following:
    • To use CIDR notation, in the Mask box, type 8, and click CIDR in the drop-down list.
    • To use a subnet mask, in the Mask box, type 2002::ff00:0, and click Mask in the drop-down list.
  7. For the Policy option, click Ignore.
  8. Click Save.
  9. Repeat Step 1 through Step 7 to add a second rule, with the following differences:
    • For Name, type Private network 192.
    • For IP address, type fe80::c0a8:0.
    • For Mask, type 16, and select CIDR in the list.

Web traffic from your organization's private network is excluded from the data that the system is processing.

Related topics

Filtering-traffic-by-using-inclusion-and-exclusion-policies

How-traffic-inclusion-and-exclusion-policies-work

Configuring-traffic-filtering-rules-on-a-Cloud-Probe

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*