Looks like you don't understand the problem. We (upstream) know perfectly
well that IPV6_V6ONLY would have made things easier, but we don't like
breaking existing setups, so we didn't change it. In our next version
(lighttpd sandbox/2.0) we already use IPV6_V6ONLY, and have a better syntax
for
severity 560837 critical
block 560238 with 560837
tag 560837 patch
thanks
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=70;bug=560238
http://redmine.lighttpd.net/projects/1/wiki/IPv4_mapped_addresses
The upstream developers do not appear to care about IPv6 and decided to
ignore the issue, but
But how to configure lighttpd to open two listening sockets?
--
Thanks,
Anatoly
pgp9Kk12ADHr7.pgp
Description: PGP signature
$SERVER[socket] == [::]:80 { }
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
this is due to an update to netbase unstable:
* Create /etc/sysctl.d/bindv6only.conf on upgrades and new installs to set
net.ipv6.bindv6only=1.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: lighttpd
Version: 1.4.25-1
Severity: important
On upgrade to version 1.4.25, this option made lighttpd only listen on
ipv6 addresses:
include_shell /usr/share/lighttpd/use-ipv6.pl
After commenting that out lighttpd was again available through ipv4.
-- System Information:
Debian
6 matches
Mail list logo
