On Fri, Mar 12, 2010 at 1:06 AM, Claudio Jeker <cje...@diehard.n-r-g.com> wrote: > > Local IPv6 redirects do not work at least not to ::1. This is a > bu^Wfeature in netinet6. It seems none of our IPv6 users care to much to > fix it (or they're equaly scared of the code). >
Hi, Thanks for the help. Redirecting to my external global address (instead of ::1) and making ftp-proxy listen on it does the trick. I don't know if adjusting the man page would be useful since I imagine the similar problem would occur with every tools requiring redirections to ::1... Index: ftp-proxy.8 =================================================================== RCS file: /cvs/src/usr.sbin/ftp-proxy/ftp-proxy.8,v retrieving revision 1.14 diff -u -r1.14 ftp-proxy.8 --- ftp-proxy.8 21 Nov 2009 13:59:31 -0000 1.14 +++ ftp-proxy.8 12 Mar 2010 11:32:24 -0000 @@ -192,3 +192,13 @@ .Pp .Nm chroots to "/var/empty" and changes to user "proxy" to drop privileges. +.Sh BUGS +There is a bug in +.Xr inet6 4 +making impossible to redirect IPv6 traffic to ::1. +If you intend to use +.Nm +in an IPv6 setup, redirect control connections to a global IPv6 address and +make +.Nm +listen on it. -- Mattieu Baptiste "/earth is 102% full ... please delete anyone you can."
