On Thu, Dec 11, 2014 at 12:35 PM, Warren Young w...@etr-usa.com wrote:
We noticed this problem when web browsers would refuse to connect to the
server. *Then* we discovered the netstat oddity, and *then* we found that
changing the Listen line in httpd.conf fixed it.
That leaves me still
On Dec 12, 2014, at 6:32 AM, Steven Tardy sjt5a...@gmail.com wrote:
On Thu, Dec 11, 2014 at 12:35 PM, Warren Young w...@etr-usa.com wrote:
We noticed this problem when web browsers would refuse to connect to the
server. *Then* we discovered the netstat oddity, and *then* we found that
Am 11.12.2014 um 04:48 schrieb Warren Young:
I’ve held off reporting this since I thought it might just be some kind of
fluke, but I’ve seen it now on three different boxes.
The symptom is that the stock configuration of Apache only listens for IPv6
connections:
$ netstat -na | grep
On Dec 11, 2014, at 3:10 AM, Alexander Dalloz ad+li...@uni-x.org wrote:
Am 11.12.2014 um 04:48 schrieb Warren Young:
the stock configuration of Apache only listens for IPv6 connections:
No, that's just the way it is displayed for apache. In fact the service
listens on IPv4 as well (given
On 12/11/2014 09:35 AM, Warren Young wrote:
Am 11.12.2014 um 04:48 schrieb Warren Young:
the stock configuration of Apache only listens for IPv6 connections:
As per RFC 3493 (Sections 3.7 and 5.3) an IPv6 socket will accept
connections from IPv4 hosts, which will be mapped into the IPv6
I’ve held off reporting this since I thought it might just be some kind of
fluke, but I’ve seen it now on three different boxes.
The symptom is that the stock configuration of Apache only listens for IPv6
connections:
$ netstat -na | grep :80.*LISTEN
tcp6 0 0 :::80
6 matches
Mail list logo
