Julian Foad wrote:
> Sigfred Håversen wrote:
>
>> Could a small patch adding an --ipv6 option to svnserve be included?
>
>
> If the patch is ready and found to be of satisfactory quality by
> tomorrow, and has a good reason for being included, then yes, it could
> be included.
>
> Can you provide such a patch or are you hoping that someone else will?
>
>> On OpenBSD a "svnserve -d -r /my/repo" would only listen on IPv6 3690:*,
>> but the common case for users is to use IPv4. The work-around is to
>> supply
>> --listen-host with a hostname resolving to an IPv4 adress, but that
>> may fail
>> if you want to listen on all interfaces.
>>
>> What I suggest is that svnserve listen on IPv4 by default, but an --ipv6
>> option gives the user the behaviour svnserve currently has.
>
>
> It's not clear to me whether that is the best solution to the problem.
> I hope someone who has worked on these IPv4/IPv6 issues before can comment.
Having just completed the IPv6 support code for CUPS 1.2, the best
thing to do is to conditionally set the IPV6_V6ONLY socket option,
e.g.:
#ifdef IPV6_V6ONLY
int val = 0;
setsockopt(fd, IPPROTO_IPV6, IPV6_V6ONLY, &val, sizeof(val));
#endif /* IPV6_V6ONLY */
I'm not sure how to do this with APR calls, but basically *BSD
defaults IPv6 sockets to only listen for IPv6 connections - you
have to use the above setsockopt magic to get a single socket
to accept both IPv6 and IPv4 connections.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Publishing Software http://www.easysw.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 21 21:30:13 2005