Of course you are right. I considered the client would be the issue and do
not now remember why I discounted it. Thank you.
On 14 April 2015 at 17:00, Eric Covener wrote:
> On Tue, Apr 14, 2015 at 6:49 AM, Mike Peachey
> wrote:
> > This client is getting responses from httpd on ports 63156+
>
>
On Tue, Apr 14, 2015 at 6:49 AM, Mike Peachey wrote:
> This client is getting responses from httpd on ports 63156+
The server side of the connection uses a well-known listening port,
443. Clients use those high ephemeral ports. I don't think tuning an
ephemeral port range on the server does any
Hi all,
Will try to be concise:
OS: Amazon Linux 2015.03 x86_64
Precise package: httpd24-2.4.12-1.60.amzn1.x86_64
Apache httpd 2.4 in use as SSL proxy.
$ sysctl net.ipv4.ip_local_port_range
net.ipv4.ip_local_port_range = 3276861000
One remote client was unable to connect. Amazon subnet ACL