Package: ziproxy
Version: 2.5.2-2
Severity: normal
Tags: ipv6
Hi.
I tested it both in lenny and squeeze version (3.1.3-1).
I set up Port and have no Address in ziproxy.conf.
According to documentation this means "bind to all interfaces".
Unfortunetly it bind to IPv4 socket.
As can be seen using netstat or ss.
$ /sbin/ss -anp | grep ziproxy
LISTEN 0 128 *:1234 *:*
users:(("ziproxy",30200,2))
$
But should be :::1234 not *:1234.
using net.ipv6.bindv6only=1 in sysctl.conf doesn't change anything.
Specifing literal IPv6 address in Address="2001:a:1:2:3:4:5:6", ends with
ziproxy listening on
broadcast address (very strange).
$ /sbin/ss -anp | grep ziproxy
LISTEN 0 128 255.255.255.255:19372 *:*
users:(("ziproxy",4219,2))
$
Putting Ipv6 address in squere brackets doesn't change anything.
So this also shows that ziproxy do not perform sufficient
parameter checking for their syntax correctnes.
Other software on the same box (apache2, sshd, ntpd, squid3 from squeeze)
listens on ipv6 without any additional configuration, by just
using default binding.
I'm currently only concerned about client side, so clients can connect
to ziproxy using IPv6. OnlyFrom and BindOutgoing, BindOutgoingExAddr
and Nextproxy will be of later consideration.
Thanks.
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to pl_PL.utf8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
