StifleR
2.10
2.10
  • Start Here - StifleR 2.10
  • Introduction
    • StifleR Overview
      • The StifleR Solution
      • Managing Microsoft Data Transfer Services
    • Technical Overview
      • 2Pint BranchCache Administrator Guide
    • Features Overview
      • Control
      • Monitor
      • Automate
      • Other Features
      • StifleR Feature Details
    • Release Notes
  • Proof of Concept
    • Objectives and Prerequisites
    • Configure Microsoft Peer-to-Peer Components
    • Install and Configure StifleR
    • Testing and Validation
    • StifleR POC Quick Checklist
  • Planning
    • StifleR Server Considerations
    • StifleR Client Considerations
    • Firewall Ports
    • Permissions
    • Antivirus Exclusions
    • Network Topology
    • StifleR Generic Concepts
      • Client Leader Roles
        • Red Leader
        • Blue Leader
        • Green Leader
        • Examples of Leader Selection
      • Templates
      • Beacons
  • Installation
    • Overview
    • Server
      • StifleR Server Installation
      • StifleR Dashboard Installation
      • StifleR Beacon Installation
    • Client
      • StifleR Client Installation
      • Post Installation Checks
  • Configuration
    • Configuration Files
      • StifleR Server Configuration File
        • Using the AppSettings Override File
      • StifleR Client Configuration File
      • StifleR Dashboard Configuration File
    • Configuring BranchCache on Windows Server
    • Configuring Delivery Optimization
    • Configuring LEDBAT on CM DPs
    • Configuring a Beacon Server
    • Configuring StifleR SQL History
    • StifleR Network Locations
      • Automatic linking of Location, Network Groups and Networks
      • Network Topology Automation
      • Location Fields
        • Network Group Fields
          • Network Fields
    • StifleRulez.xml Configuration Guide
      • The Match – TypeData
        • When the Job Title Isn’t Suitable
        • ConfigMgr Specific Rules
      • The Setting - DownloadTypes
        • Delivery Optimization Jobs
      • Sample StifleRulez.xml
    • Securing StifleR Operations with SSL
      • Prerequisites
      • Using a Web Server Certificate
        • Requesting a Web Server Certificate
      • Using a Self-Signed Certificate
      • Preparing the StifleR Dashboard Web Site for SSL
      • Configuring StifleR to Use SSL
      • Finding the Certificate Thumbprint
    • StifleR Client Access Control Options
  • Operations
    • Dashboard
      • Overview & Navigation
        • Home Page
        • Traffic & Downloads
          • Transfers & Downloads
            • How to use query hosts search?
          • Running Sequences
          • Weekly Downloads Activity
          • History
        • Devices
          • Clients
            • Client Details
              • How to use an extended search?
          • Servers
          • StifleR Server
            • Templates Detail
        • Cache Management
        • System Resource Usage
        • Network Topology
          • Maps
          • Countries
          • Locations
            • Bandwidth Allocations and Locations
          • Network Groups
          • Networks
        • Reporting & Diagrams
    • Client Management & Remote Tools
      • Remote PowerShell Session
      • Remote Performance Counter
      • Remote WMI Browsing
      • Remote Event Log Viewer
      • Remote Netmon Session
    • Monitoring
      • StifleR server health
      • StifleR client health
      • BranchCache Testing and Monitoring
    • Maintenance tasks
    • Bandwidth Management and Allocation
      • Bandwidth Tuning Monitoring and Control
    • Backup and Recovery
      • Moving the StifleR Server Databases to a New Drive on the Same Server
    • Troubleshooting
      • StifleR Client Command Line Options
      • BranchCache across Subnets
    • StifleR WMI Provider
Powered by GitBook
On this page
  1. Configuration
  2. StifleR Network Locations

Automatic linking of Location, Network Groups and Networks

PreviousStifleR Network LocationsNextNetwork Topology Automation

Last updated 1 year ago

External addresses (NAT:ed networks)

Automatic networking linking

There are two types of automatic linking;

  1. Linking to an existing network, where the network is a phycially attached network that is routable from one to another. This can be a subnet that is defined as a different vlan on the same layer 3 switch.

  2. Networks that are in the same physical premise but is not routable directly within the same physical location. This could be the case where we have a WiFi network that is using central switching that is in the same physical location as another wired network. The networks are only routable via a central route (i.e. datacenter).

Routing detection

Route tracert is key for automatic link detection. There are two types of tracert testing;

  1. ICMP based tracert sessions

  2. TCP based tracert sessions [BETA]

We strongly recommend using the Beacons to define the place for the routing tests. As the beacon is defined on the networking group level, the following logic instructs the client to find it’s best beacon;

  1. Geo data

  2. Routing data to

Same network linking

We judge if the network is in the same physical network via;

  1. The network routing information

  2. If we return a route information from client this is compared to an already existing route, if there is a match on the second and third routes the location is deemed to be the same.

  3. If the route is the same, we test TCP connection data across on the BranchCache or DO ports to ensure we have a platform for P2P traffic to flow.

  4. If this test fails the location will be added in the same physical location but as a separate networking group.

  5. If we have no routing information or if the route data is inconsistent we check the machines gateway information by using the MAC address. If we find a match within 5 (configurable) bits on the MAC address we then test those locations for;

  6. If there is a direct link to that network using the TCPPing options.

  7. In case of a successful test, we then add the subnet to the same network group as the first item.

If the matching location has no Geo Data set, we then add the incoming geo location data (not for VPN).