[jira] [Commented] (TS-698) LogFilter should support an actual IP type and matching rules
[
https://issues.apache.org/jira/browse/TS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096142#comment-14096142
]
ASF subversion and git services commented on TS-698:
Commit 43bec913f59a7542ee8e1ff76bdc365f18664102 in trafficserver's branch
refs/heads/master from [~amc]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=43bec91 ]
TS-698: Add IP filter to logging.
LogFilter should support an actual IP type and matching rules
-
Key: TS-698
URL: https://issues.apache.org/jira/browse/TS-698
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Affects Versions: 2.1.6
Environment: N/A
Reporter: Eric Connell
Assignee: Alan M. Carroll
Priority: Minor
Labels: review
Fix For: 5.1.0
Attachments: logfilterip.patch
The LogFilter configuration in logs_xml.config should support a native IPv4
and IPv6 filtering. For example, it would be handy to be able to filter out
log lines from a specific server or netblock. For example, the following
config would reject log lines for all hosts in the 10/8 network:
{code}
LogFilter
Name = local_net/
Condition = chi MATCH 10.0.0.0/8/
Action = REJECT/
/LogFilter
LogFormat
Name = access_log/
Format = %shi/
/LogFormat
LogObject
Format = access_log/
Filename = access_log/
Filters = local_net/
/LogObject
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-698) LogFilter should support an actual IP type and matching rules
[
https://issues.apache.org/jira/browse/TS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14096145#comment-14096145
]
ASF subversion and git services commented on TS-698:
Commit 5257ec7d42b561a5e8bea6357a5a4e2a107c5b54 in trafficserver's branch
refs/heads/master from [~econnell]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=5257ec7 ]
TS-698: Add IP filter to logging. Update CHANGES and correct author.
LogFilter should support an actual IP type and matching rules
-
Key: TS-698
URL: https://issues.apache.org/jira/browse/TS-698
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Affects Versions: 2.1.6
Environment: N/A
Reporter: Eric Connell
Assignee: Alan M. Carroll
Priority: Minor
Labels: review
Fix For: 5.1.0
Attachments: logfilterip.patch
The LogFilter configuration in logs_xml.config should support a native IPv4
and IPv6 filtering. For example, it would be handy to be able to filter out
log lines from a specific server or netblock. For example, the following
config would reject log lines for all hosts in the 10/8 network:
{code}
LogFilter
Name = local_net/
Condition = chi MATCH 10.0.0.0/8/
Action = REJECT/
/LogFilter
LogFormat
Name = access_log/
Format = %shi/
/LogFormat
LogObject
Format = access_log/
Filename = access_log/
Filters = local_net/
/LogObject
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-698) LogFilter should support an actual IP type and matching rules
[
https://issues.apache.org/jira/browse/TS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094836#comment-14094836
]
Alan M. Carroll commented on TS-698:
I'm reviewing this and doing some tweaks. Did this compile? I have problems
because the wipe_this_entry method is missing from LogFilterIP.
LogFilter should support an actual IP type and matching rules
-
Key: TS-698
URL: https://issues.apache.org/jira/browse/TS-698
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Affects Versions: 2.1.6
Environment: N/A
Reporter: Eric Connell
Assignee: Alan M. Carroll
Priority: Minor
Labels: review
Fix For: 5.1.0
Attachments: logfilterip.patch
The LogFilter configuration in logs_xml.config should support a native IPv4
and IPv6 filtering. For example, it would be handy to be able to filter out
log lines from a specific server or netblock. For example, the following
config would reject log lines for all hosts in the 10/8 network:
{code}
LogFilter
Name = local_net/
Condition = chi MATCH 10.0.0.0/8/
Action = REJECT/
/LogFilter
LogFormat
Name = access_log/
Format = %shi/
/LogFormat
LogObject
Format = access_log/
Filename = access_log/
Filters = local_net/
/LogObject
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-698) LogFilter should support an actual IP type and matching rules
[
https://issues.apache.org/jira/browse/TS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982664#comment-13982664
]
Leif Hedstrom commented on TS-698:
--
[~amc] Can you review this? If not, unassign it (or assign it to me).
LogFilter should support an actual IP type and matching rules
-
Key: TS-698
URL: https://issues.apache.org/jira/browse/TS-698
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Affects Versions: 2.1.6
Environment: N/A
Reporter: Eric Connell
Assignee: Alan M. Carroll
Priority: Minor
Labels: review
Fix For: 5.0.0
Attachments: logfilterip.patch
The LogFilter configuration in logs_xml.config should support a native IPv4
and IPv6 filtering. For example, it would be handy to be able to filter out
log lines from a specific server or netblock. For example, the following
config would reject log lines for all hosts in the 10/8 network:
{code}
LogFilter
Name = local_net/
Condition = chi MATCH 10.0.0.0/8/
Action = REJECT/
/LogFilter
LogFormat
Name = access_log/
Format = %shi/
/LogFormat
LogObject
Format = access_log/
Filename = access_log/
Filters = local_net/
/LogObject
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-698) LogFilter should support an actual IP type and matching rules
[
https://issues.apache.org/jira/browse/TS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13982087#comment-13982087
]
Jay Tomolek commented on TS-698:
hi,
i've developed a patch to handle this issue allowing MATCH operator over
LogField::IP fields (chi, shi, phi).
it was implemented as LogFilterIP, quite similiar to LogFilterInt code,
allowing single or multiple IP matchs (comma separated) , such as:
LogFilter
Name = reject_localhost_requests/
Condition = chi MATCH 127.0.0.1/
Action = REJECT/
/LogFilter
LogFilter
Name = apache_org_responses/
Condition = chi MATCH 192.87.106.229,140.211.11.131/
Action = ACCEPT/
/LogFilter
LogFilter should support an actual IP type and matching rules
-
Key: TS-698
URL: https://issues.apache.org/jira/browse/TS-698
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Affects Versions: 2.1.6
Environment: N/A
Reporter: Eric Connell
Assignee: Alan M. Carroll
Priority: Minor
Fix For: sometime
The LogFilter configuration in logs_xml.config should support a native IPv4
and IPv6 filtering. For example, it would be handy to be able to filter out
log lines from a specific server or netblock. For example, the following
config would reject log lines for all hosts in the 10/8 network:
{code}
LogFilter
Name = local_net/
Condition = chi MATCH 10.0.0.0/8/
Action = REJECT/
/LogFilter
LogFormat
Name = access_log/
Format = %shi/
/LogFormat
LogObject
Format = access_log/
Filename = access_log/
Filters = local_net/
/LogObject
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (TS-698) LogFilter should support an actual IP type and matching rules
[
https://issues.apache.org/jira/browse/TS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13876341#comment-13876341
]
Leif Hedstrom commented on TS-698:
--
[~amc] Are you going to work on this? If not, move back to pool. Also, if this
is not something we should / could work on, close. Marking as sometime for
now.
LogFilter should support an actual IP type and matching rules
-
Key: TS-698
URL: https://issues.apache.org/jira/browse/TS-698
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Affects Versions: 2.1.6
Environment: N/A
Reporter: Eric Connell
Assignee: Alan M. Carroll
Priority: Minor
Fix For: sometime
The LogFilter configuration in logs_xml.config should support a native IPv4
and IPv6 filtering. For example, it would be handy to be able to filter out
log lines from a specific server or netblock. For example, the following
config would reject log lines for all hosts in the 10/8 network:
{code}
LogFilter
Name = local_net/
Condition = chi MATCH 10.0.0.0/8/
Action = REJECT/
/LogFilter
LogFormat
Name = access_log/
Format = %shi/
/LogFormat
LogObject
Format = access_log/
Filename = access_log/
Filters = local_net/
/LogObject
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (TS-698) LogFilter should support an actual IP type and matching rules
[
https://issues.apache.org/jira/browse/TS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13083874#comment-13083874
]
Zhao Yongming commented on TS-698:
--
LogFilter.cc:456 // Long term we should move IPs to their own log type.
we have not just two kinds of filter, string and int, we may need to setup the
IP type
LogFilter should support an actual IP type and matching rules
-
Key: TS-698
URL: https://issues.apache.org/jira/browse/TS-698
Project: Traffic Server
Issue Type: Improvement
Components: Logging
Affects Versions: 2.1.6
Environment: N/A
Reporter: Eric Connell
Priority: Minor
Fix For: 3.1.1
The LogFilter configuration in logs_xml.config should support a native IPv4
and IPv6 filtering. For example, it would be handy to be able to filter out
log lines from a specific server or netblock. For example, the following
config would reject log lines for all hosts in the 10/8 network:
{code}
LogFilter
Name = local_net/
Condition = chi MATCH 10.0.0.0/8/
Action = REJECT/
/LogFilter
LogFormat
Name = access_log/
Format = %shi/
/LogFormat
LogObject
Format = access_log/
Filename = access_log/
Filters = local_net/
/LogObject
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
