[Pound Mailing List] setting up pound listeners for dual stack IPv4 and IPv6`

Chris Harrison <[email protected]>
Newsgroups gmane.comp.web.pound.general
Message-ID <[email protected]>
hello All,
I hope this list can help me.

I have had difficulty finding any references to setting up pound with 
IPv6 especially in a dual stack environment.
I already have a Heartbeat supported IPv4 Pound installation.  I have a 
listener on port 80 that redirects to the ssl version on port 443.  from 
there haproxy listens to 127.0.0.1 and load balances between IPv4 web 
servers.  I want to have the same ports on the IPv6 address do they same 
thing.  if i remove the IPv6 listeners the IPv4 work.  if I add the IPv6 
listeners i get
I think that they should look like this (actual data hidden):
/etc/pound.cfg

#pre-existing and working

#servername -IPv4 listener
ListenHTTP
     Address xxx.xxx.xxx.20
     port    80
     xhttp   2
     Service
         Redirect    "https://servername"
     End
End

#servername - ssl
ListenHTTPS
         Address xxx.xxx.xxx.20
         Port 443
         Cert "/etc/servername.pem"
         Service
                 BackEnd
                         Address 127.0.0.127
                         Port 80
                 End
         End
End

#how I think the the IPv6 should look but doesn't work

#servername -ipv6 listener
ListenHTTP
     Address yyyy:yyyy:yyyyy:yyyyy::20
     port    80
     xhttp   2
     Service
         Redirect    "https://servername"
     End
End

#servername - IPv6 -ssl
ListenHTTPS
         Address yyyy:yyyy:yyyy:yyyy::20
         Port 443
         Cert "/etc/servername.pem"
         Service
                 BackEnd
                         Address 127.0.0.127
                         Port 80
                 End
         End
End

127.0.0.127:80 is the HAproxy load balancer to the back end IPv4 web 
servers.

Any suggestions about what i am missing?
Thanks
Taz
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.