IPv6 support
Session-level and advanced session-level policies support both IPv4 and IPv6 addresses. Any IPv6 notation is supported.
Example:
SR_POLICIES
{
IF (CLIENT_IP = '::ffff:150.49.108.36')
{
TRANSFORM_SOURCE_PROGRAM MATCH_PATTERN = '^.*$' OUTPUT_FORMAT = 'SPECIAL JDBC'
}
}
SR_POLICIES
{
IF (CLIENT_IP = '150.49.108.36')
{
TRANSFORM_SOURCE_PROGRAM MATCH_PATTERN = '^.*$' OUTPUT_FORMAT = 'SPECIAL JDBC'
}
}
This shows two logically equal rule conditions using IPv6 and IPv4 notation.Example:
SR_POLICIES
{
IF (SERVER_IP = ('',1) SERVER_PORT = 1521)
{
TRANSFORM_SOURCE_PROGRAM MATCH_PATTERN = '^.*$' OUTPUT_FORMAT = 'SPECIAL JDBC'
}
GROUP_ID = 1 TYPE = IP_ADDRESS SIZE = 2 #CLIENT_IP GROUP
{
'150.49.108.36' '2002:920:C000:3146::6'
}
}
This example shows a policy for a database server with dual IPv4 and IPv6 addresses.Example:
SR_POLICIES
{
IF (CLIENT_IP = '::FFFF:DCCC:ED91' CLIENT_NET_MASK = '::FFFF:DCCC:0000' SENDER_IP = '2002:920:C000:3146::6')
{
TRANSFORM_OS_USER MATCH_PATTERN = '^.*$' OUTPUT_FORMAT = 'SPECIAL OS_USER'
}
}
This shows how network masks for IPv6 addresses are supported in a format similar to
IPv4.Example:
SR_POLICIES
{
IF (CLIENT_IP = '0.0.0.0' SERVER_IP = '9.70.157.177' ANALYZED_CLIENT_IP = '9.70.144.184' ANALYZED_CLIENT_NET_MASK = '255.255.255.0')
{
TRANSFORM_SERVER_DESC SEARCH_PREFIX = '9.' SOURCE = ANALYZED_CLIENT_IP OUTPUT_FORMAT = '(.*)'
}
}
SR_POLICIES
{
IF (CLIENT_IP = '0.0.0.0' SERVER_IP = '9.70.157.177' ANALYZED_CLIENT_IP = '::ffff:9.70.144.184' ANALYZED_CLIENT_NET_MASK = '::ffff:0000:0000')
{
TRANSFORM_SERVER_DESC SEARCH_PREFIX = '9.' SOURCE = ANALYZED_CLIENT_IP OUTPUT_FORMAT = '(.*)'
}
}
This shows using ANALYZED_CLIENT_IP as condition with IPv4 and IPv6 addresses. The rule
copies the value from the column ANALYZED_CLIENT_IP into the column SERVER_DESC of table
GDM_ACCESS.