You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Michael Turner (JIRA)" <ji...@apache.org> on 2012/04/30 23:33:56 UTC
[jira] [Created] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Michael Turner created TS-1235:
----------------------------------
Summary: Deny occurring for IPs not in the ip_allow.config file
Key: TS-1235
URL: https://issues.apache.org/jira/browse/TS-1235
Project: Traffic Server
Issue Type: Bug
Components: Configuration, Security
Affects Versions: 3.1.3
Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Michael Turner
Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
#
# ip_allow.config
#
# Two types of rules:
# #src_ip=<range of IP addresses> action=ip_allow
# #src_ip=<range of IP addresses> action=ip_deny
# Rules are applied in the order listed starting from the top.
#
# Ban all of the XXXX servers
src_ip=AAA.BBB.CCC.134 action=ip_deny
#src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
src_ip=AAA.BBB.CCC.137 action=ip_deny
src_ip=AAA.BBB.CCC.202 action=ip_deny
src_ip=AAA.BBB.CCC.203 action=ip_deny
src_ip=AAA.BBB.CCC.208 action=ip_deny
src_ip=AAA.BBB.CCC.209 action=ip_deny
src_ip=AAA.BBB.CCC.216 action=ip_deny
src_ip=AAA.BBB.CCC.217 action=ip_deny
src_ip=AAA.BBB.CCC.218 action=ip_deny
src_ip=AAA.BBB.CCC.219 action=ip_deny
src_ip=AAA.BBB.CCC.220 action=ip_deny
src_ip=AAA.BBB.CCC.222 action=ip_deny
src_ip=AAA.BBB.CCC.224 action=ip_deny
src_ip=AAA.BBB.CCC.236 action=ip_deny
# Banned IPs
src_ip=AAA.BBB.CCC.212 action=ip_deny
src_ip=AAA.BBB.CCC.246 action=ip_deny
src_ip=AAA.BBB.CCC.144 action=ip_deny
# Stock Rules
src_ip=0.0.0.0-255.255.255.255 action=ip_allow
src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
And here's log entries from when this config was active:
[Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
[Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
[Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
[Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
[Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
[Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
[Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
[Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
[Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
[Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
[Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
FATAL: HttpSM.cc:890: failed assert `0`
The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277009#comment-13277009 ]
Alan M. Carroll commented on TS-1235:
-------------------------------------
I am looking at this now and can not replicate it on 3.1.3. If possible, the reporter should do a debug build and enable the "ip-allow" debug tag and see if the output makes sense. In particular whether the addresses in question are listed as allow or deny. It looks fine here on 3.1.3 (although I think it was broken in 3.1.2). I will try to set up a more thorough test to get more information.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.1.4
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413740#comment-13413740 ]
Alan M. Carroll edited comment on TS-1235 at 7/13/12 2:05 PM:
--------------------------------------------------------------
OK, I will look in to that.
I can't replicate it - can you enable debug with the "ip-allow" tag?
was (Author: amc):
OK, I will look in to that.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413740#comment-13413740 ]
Alan M. Carroll edited comment on TS-1235 at 7/13/12 2:21 PM:
--------------------------------------------------------------
OK, I will look in to that.
I can't replicate it - can you enable debug with the "ip-allow" tag?
How rapidly does this fail? Almost immediately or after a while?
was (Author: amc):
OK, I will look in to that.
I can't replicate it - can you enable debug with the "ip-allow" tag?
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "David Carlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448452#comment-13448452 ]
David Carlin commented on TS-1235:
----------------------------------
Kingsley,
My coworker did the following:
sudo traffic_line -s proxy.config.http.insert_response_via_str -v 1; sudo traffic_line -x 1
and an hour later, all ~30 boxes crashed. Same this happened 2nd time this setting was enabled. Same "WARNING: connect by disallowed client" and stack trace in traffic.out as you mention above.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Michael Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279164#comment-13279164 ]
Michael Turner commented on TS-1235:
------------------------------------
We have production stable at this point so I'm not sure if I'll be able to get a debug build set up with the traffic that manifested this, but I'll see what I can do.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.1.4
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1235:
------------------------------
Fix Version/s: 3.1.4
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.1.4
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279133#comment-13279133 ]
Alan M. Carroll commented on TS-1235:
-------------------------------------
After more testing, I still can't replicate this problem even with 3.1.3.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.1.4
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Kingsley Foreman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448279#comment-13448279 ]
Kingsley Foreman commented on TS-1235:
--------------------------------------
what option is Via: headers in records?
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "David Carlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413776#comment-13413776 ]
David Carlin commented on TS-1235:
----------------------------------
I filed a bug TS-1329 that might be the same issue. Bryan Call pointed out that according to the source code, this error message is from someone trying to connect to the management port that is not from 127.0.0.1 - so not sure if its ip_allow.config related?
It happens very infrequently for me; I've only seen it twice, we have many machines running ATS.
My ip_allow.config:
src_ip=0.0.0.0-255.255.255.255 action=ip_allow method=ALL
src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow method=ALL
We then have a custom plugin (our only running plugin) that does quick filtering permission on a list of subnets.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413740#comment-13413740 ]
Alan M. Carroll commented on TS-1235:
-------------------------------------
OK, I will look in to that.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll reassigned TS-1235:
-----------------------------------
Assignee: Alan M. Carroll
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1235:
------------------------------
Fix Version/s: (was: 3.1.4)
3.3.0
Moving out to 3.3.0 until we can get reproducible test case.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.0
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Kingsley Foreman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413820#comment-13413820 ]
Kingsley Foreman commented on TS-1235:
--------------------------------------
Sorry I should have mentioned it took about 2 hours (on a very busy box) before it did it.
I did a reload not a restart.
I will do some debugging on monday (it is Sat morning here).
Kingsley
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "David Carlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449221#comment-13449221 ]
David Carlin commented on TS-1235:
----------------------------------
It appears that proxy.config.http.insert_response_via_str isn't the cause of the problem. We set this on the same boxes but restarted ats this time instead of reloading config via traffic_line and are NOT seeing the crashes.
What is interesting is that I see the following in traffic.out when I run "sudo traffic_line -x 1" even though I didn't touch ip_allow.config (or any other settings):
[Sep 5 22:31:34.673] Manager {0x7fe87d554700} NOTE: User has changed config file ip_allow.config
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Kingsley Foreman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448453#comment-13448453 ]
Kingsley Foreman commented on TS-1235:
--------------------------------------
I have set to
CONFIG proxy.config.http.insert_response_via_str INT 0
but I did find this happened after we reloaded the config.
After a clean start it appeared to work OK.
Kingsley
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413740#comment-13413740 ]
Alan M. Carroll edited comment on TS-1235 at 7/13/12 2:24 PM:
--------------------------------------------------------------
OK, I will look in to that.
I can't replicate it - can you enable debug with the "ip-allow" tag?
How rapidly does this fail? Almost immediately or after a while?
Do you edit the ip_allow.config and then restart ATS, or update while running?
was (Author: amc):
OK, I will look in to that.
I can't replicate it - can you enable debug with the "ip-allow" tag?
How rapidly does this fail? Almost immediately or after a while?
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273028#comment-13273028 ]
Leif Hedstrom commented on TS-1235:
-----------------------------------
I hope that assert is from the SSL bug James is working on?
Alan: You want me to look at this ?
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.1.4
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Alan M. Carroll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll updated TS-1235:
--------------------------------
Comment: was deleted
(was: Possibly the same bug.)
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "David Carlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448458#comment-13448458 ]
David Carlin commented on TS-1235:
----------------------------------
Interesting - I shall see if simply "traffic_line -x 1" will cause the crash to appear later on, or if changing any setting and then reloading does it. Thanks!
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "David Carlin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447844#comment-13447844 ]
David Carlin commented on TS-1235:
----------------------------------
Did you guys by any chance have Via: headers enabled when this problem occurred? I'm seeing the same stack trace, same "WARNING: connect by disallowed client" msgs in traffic.out - but it is much more reproducible when Via: headers turned on. Happens about an hour after enabling it. See TS-1329.
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.3
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1235) Deny occurring for IPs not in the
ip_allow.config file
Posted by "Kingsley Foreman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413725#comment-13413725 ]
Kingsley Foreman commented on TS-1235:
--------------------------------------
I was just also hit by this one,
53.703] Server {0x2b692129f700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.704] Server {0x2b691de249a0} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.709] Server {0x2b691fc89700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.713] Server {0x2b691fd8a700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.723] Server {0x2b691fe8b700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.724] Server {0x2b691ff8c700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.724] Server {0x2b692008d700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.731] Server {0x2b6920390700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.732] Server {0x2b6920491700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.735] Server {0x2b6920592700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.742] Server {0x2b6920693700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.743] Server {0x2b6920794700} WARNING: connect by disallowed client 127.0.0.1, closing
[Jul 13 19:22:53.746] Server {0x2b6920895700} WARNING: connect by disallowed client 127.0.0.1, closing
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/bin/traffic_server - STACK TRACE:
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/bin/traffic_server - STACK TRACE:
/lib/libpthread.so.0(+0xf8f0)[0x2b691b0f98f0]
/usr/lib/libtsutil.so.3(_ZNK5IpMap8containsEPK8sockaddrPPv+0xb1)[0x2b691aed3201]
/usr/bin/traffic_server(_ZN10HttpAccept9mainEventEiPv+0x254)[0x50aa24]
/usr/bin/traffic_server(_ZN18UnixNetVConnection11acceptEventEiP5Event+0x3d6)[0x65e6d6]
NOTE: Traffic Server received Sig 11: Segmentation fault
/usr/bin/traffic_server - STACK TRACE:
/usr/bin/traffic_server(_ZN7EThread13process_eventEP5Eventi+0xb4)[0x67c814]
/lib/libpthread.so.0(+0xf8f0)[0x2b691b0f98f0]
/lib/libpthread.so.0(+0xf8f0)[0x2b691b0f98f0]
/usr/bin/traffic_server(_ZN7EThread7executeEv+0x5ab)[0x67d29b]
/usr/bin/traffic_server[0x67aeb2]
/lib/libpthread.so.0(+0x69ca)[0x2b691b0f09ca]
/lib/libc.so.6(clone+0x6d)[0x2b691d73dcdd]
/usr/lib/libtsutil.so.3(_ZNK5IpMap8containsEPK8sockaddrPPv+0xb1)[0x2b691aed3201]
I can tell you what I changed
I changed
src_ip=127.0.0.1 action=ip_allow
src_ip=0.0.0.0-255.255.255.255 action=ip_deny
to
src_ip=127.0.0.1 action=ip_deny method=PUSH|PURGE|DELETE
src_ip=0.0.0.0-255.255.255.255 action=ip_deny
> Deny occurring for IPs not in the ip_allow.config file
> ------------------------------------------------------
>
> Key: TS-1235
> URL: https://issues.apache.org/jira/browse/TS-1235
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 3.1.3
> Environment: Linux server.domain.com 2.6.32-220.el6.x86_64 #1 SMP Wed Dec 7 10:41:06 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Michael Turner
> Assignee: Alan M. Carroll
> Fix For: 3.3.2
>
>
> Consistently seeing this morning IPs that are not set to deny in ip_allow.config being rejected. Here's the config file we were using:
> #
> # ip_allow.config
> #
> # Two types of rules:
> # #src_ip=<range of IP addresses> action=ip_allow
> # #src_ip=<range of IP addresses> action=ip_deny
> # Rules are applied in the order listed starting from the top.
> #
> # Ban all of the XXXX servers
> src_ip=AAA.BBB.CCC.134 action=ip_deny
> #src_ip=AAA.BBB.CCC.135 action=ip_deny # temp unbanning. we've talked to him
> src_ip=AAA.BBB.CCC.137 action=ip_deny
> src_ip=AAA.BBB.CCC.202 action=ip_deny
> src_ip=AAA.BBB.CCC.203 action=ip_deny
> src_ip=AAA.BBB.CCC.208 action=ip_deny
> src_ip=AAA.BBB.CCC.209 action=ip_deny
> src_ip=AAA.BBB.CCC.216 action=ip_deny
> src_ip=AAA.BBB.CCC.217 action=ip_deny
> src_ip=AAA.BBB.CCC.218 action=ip_deny
> src_ip=AAA.BBB.CCC.219 action=ip_deny
> src_ip=AAA.BBB.CCC.220 action=ip_deny
> src_ip=AAA.BBB.CCC.222 action=ip_deny
> src_ip=AAA.BBB.CCC.224 action=ip_deny
> src_ip=AAA.BBB.CCC.236 action=ip_deny
> # Banned IPs
> src_ip=AAA.BBB.CCC.212 action=ip_deny
> src_ip=AAA.BBB.CCC.246 action=ip_deny
> src_ip=AAA.BBB.CCC.144 action=ip_deny
> # Stock Rules
> src_ip=0.0.0.0-255.255.255.255 action=ip_allow
> src_ip=::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff action=ip_allow
> And here's log entries from when this config was active:
> [Apr 30 10:06:21.446] {0x2b321b2d42a0} NOTE: updated diags config
> [Apr 30 10:06:21.449] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.492] Server {0x2b321b2d42a0} NOTE: cache clustering disabled
> [Apr 30 10:06:21.584] Server {0x2b321b2d42a0} NOTE: logging initialized[15], logging_mode = 3
> [Apr 30 10:06:21.591] Server {0x2b321b2d42a0} NOTE: traffic server running
> [Apr 30 10:06:25.140] Server {0x2b3222d2c700} NOTE: cache enabled
> [Apr 30 10:06:33.804] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:01.914] Server {0x2b324b2d2700} WARNING: connect by disallowed client AAA.BBB.CCC.111, closing
> [Apr 30 10:07:02.025] Server {0x2b324b4d4700} WARNING: connect by disallowed client AAA.BBB.CCC.144, closing
> [Apr 30 10:07:03.109] Server {0x2b3222827700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:04.594] Server {0x2b3222f2e700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:05.201] Server {0x2b3223332700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.170] Server {0x2b3223534700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.575] Server {0x2b3223736700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.690] Server {0x2b3223837700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.785] Server {0x2b3223938700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.817] Server {0x2b3223a39700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:06.841] Server {0x2b3223b3a700} WARNING: connect by disallowed client AAA.BBB.CCC.74, closing
> [Apr 30 10:07:10.587] Server {0x2b321b2d42a0} WARNING: connect by disallowed client AAA.BBB.CCC.35, closing
> FATAL: HttpSM.cc:890: failed assert `0`
> The IPS visible in the log ending in .111 and .74 are not in the deny list anywhere. The two ending in .144 and .35 are in the deny list.
> Please let me know what further information I can provide to help troubleshoot/reproduce this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira