infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Commented] (INFRA-16599) My subnet appears to be blocked or banned by
Date Thu, 31 May 2018 01:23:00 GMT


Chris Lambertus commented on INFRA-16599:

I've unbanned (that was the only block on that subnet.) If it happens again,
you will be auto banned again.

> My subnet appears to be blocked or banned by
> -----------------------------------------------------------------------
>                 Key: INFRA-16599
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: HTTP Server
>         Environment: Red Hat Enterprise Linux 7.4 and Debian Buster and Debian Sid on
x86_64 and POWER as well as Solaris on SPARC
>            Reporter: Dennis Clarke
>            Assignee: Chris Lambertus
>            Priority: Blocker
> Apache folks :
>     Something strange happened in the last 36 hours or so. I was working
> away on a trunk build of httpd in order to test tls 1.3 per :
>     Bug 62413 - SSLProtocol: Illegal protocol 'TLSv1.3'
> Not really a "bug" but a feature that is enabled on the trunk but not in
> mod_ssl for 2.4.33 but regardless to do anything I need to be able to :
> $ svn checkout httpd-trunk
> svn: E170013: Unable to connect to a repository at URL ''
> svn: E000110: Error running context: Connection timed out
> Even sites such as are non-responsive.
> However only from one subnet and not on another. Both are well known
> and arin registered subnets.
> However that was working fine for me 36 hours ago. Also, nearly every
> site in the domain will not respond from my local subnet but
> I am able to access those sites from another subnet at the office. So
> then, the question is, what is going on here?  Is there a "fail2ban"
> type ip block service in place somewhere that is blocking packets?
> Dennis 
> ps: I created this jira entry from yet another separate subnet

This message was sent by Atlassian JIRA

View raw message