The main part of External Repository is that the user can define rules for accessing the repository location. The main purpose of using repository rules there by allowing the users to stream packages from the nearby streaming server based on defined rules. The rules can be defined based on User, IP and User Group.
Before proceeding with this the user should have created valid Repository location as shown below.
User based Rules:
For example, if you set rule as following
“Match any Demouser
Stream from \\ExternalRepo\TestLocation”
It means allow Demouser to stream packages from the location \\ExternalRepo\TestLocation
In the similar way if you set rule as following
“Match any
Stream from \\ExternalRepo\TestLocation”
It means allow all users to stream packages from the location \\ExternalRepo\TestLocation
IP based Rules:
For example, if you set rule as following
“Match ip 10.223.9.*
Stream from \\ExternalRepo\Chennai”
It means allow IP range 10.223.9.1 to 10.223.9.254 to stream packages from Chennai location.
In the similar way if you set rule with CIDR (Classless Inter-Domain Routing) notation as following
“Match ip 10.223.11.0/24
Stream from \\ExternalRepo\Pune”
It means allow IP range 10.223.11.1 to 10.223.11.254 to stream packages from Pune location.
Refer to this URL (http://www.pantz.org/software/tcpip/subnetchart.html) regarding how to set CIDR notation.
Note: While streaming via Proxy server you should be very careful while setting the rules.
User Group based Rules:
For example, if you set rule as following
“Match group EMM
Stream from \\ExternalRepo\Bangalore”
It means allow EMM group users to stream packages from Bangalore location
In the similar way if you set rule as following
“Match group
Stream from \\ExternalRepo\Bangalore”
It means allow all groups to stream packages from Bangalore location.
Prioritizing the Repository Rules:
The created rules can prioritized by dragging rules below or above.
If the rules set as shown in above screenshot, if the user streams package from his client machine (10.223.9.75), the packages always gets streamed from Chennai Repository location even though we have set rule saying if the client machine (10.223.9.75), the package should get streamed from Pune Repository location. It does not happen, which is the expected behavior.
Now after prioritizing the rules as shown in below screenshot
If the user streams package from his client machine (10.223.9.75), the packages always gets streamed from Pune Repository location not from Chennai Repository location. Note: if the user streams package from other client machines, the package should get streamed from Chennai Repository location.