<ipfilter name="filter2" type="permissive"> <deny ip="22.214.171.124/255.255.255.0"/> <allow ip="126.96.36.199/255.255.255.255"/> <appliesto tagref="samoht"/> <appliesto tagref="noside"/> </ipfilter>
|ipfilter name="filter2"||The filter name. Uniquely identifies the filter.|
|type="permissive"||The filter type.
This term identifies whether the filter is permissive or restrictive and indicates the order of IP testing (deny and allow) that it can perform on an incoming IP address.
|<deny ip="188.8.131.52/255.255.255.0"/>||The deny element appears first in a permissive filter.
The deny element is divided into two segments, separated by a slash (/):
You can use the deny element in a permissive filter to specify a higher network tree level than what you specify in the allow element.
|<allow ip="184.108.40.206 /255.255.255.255"/>||The allow element must appear after the deny element in a permissive filter.
The allow element is divided into two segments, separated by a / :
You can use the allow element in a permissive filter to specify a lower level in the network tree than what you use for the deny element, to allow exceptions to the IPs that the filter explicitly denies. If necessary, you can use multiple allow elements to define the exceptions.
|appliesto tagref="samoht"||Identifies a user affected by this set of filter rules.
Each appliesto tagref value must correspond to a tag attribute for an individual Teradata Database user listed in a user element of the XML IP restriction document.
|appliesto tagref="noside"||Identifies a second user affected by this set of filter rules.|