apache2 w/ ipv6 kills ipv4 connections

[Peter Avalos <pavalos@xxxxxxxxxxxx>]

The topic doesn't quite tell the exact story of the problem, but it's
an interesting problem.

I installed apache2 from ports with ipv6 support.  When I started up
the server, ipv6 connections worked great, but I'd get connection
refused about 80% of the time with ipv4.

netstat:
  0 tcp46      0      0 *.80                  *.*                   LISTEN

sockstat -6:
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS      
www      httpd    91500    3 0      0                     *:80                 
www      httpd    91493    3 0      0                     *:80                 
www      httpd    91492    3 0      0                     *:80                 
www      httpd    91491    3 0      0                     *:80                 
www      httpd    91490    3 0      0                     *:80                 
www      httpd    91489    3 0      0                     *:80                 
root     httpd    91487    3 0      0                     *:80                 

Nothing shows up in sockstat -4 that's listening on port 80.

When I compiled the port WITHOUT_IPV6, the ipv4 connection refused problem
disappeared.

netstat:
  0 tcp4       0      0 *.80                  *.*                   LISTEN

sockstat -4:
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS      
www      httpd    50438    3 0      0                     *:80                 
www      httpd    50415    3 0      0                     *:80                 
www      httpd    50413    3 0      0                     *:80                 
www      httpd    50412    3 0      0                     *:80                 
www      httpd    50411    3 0      0                     *:80                 
www      httpd    50410    3 0      0                     *:80                 
www      httpd    50409    3 0      0                     *:80                 
root     httpd    50407    3 0      0                     *:80                 

I don't think this is an apache problem, but I can't verify that.  Anyone
have any ideas?

--Pete