Ok that does in fact fix it for me no patch required...
adding --listen-host=0.0.0.0, forced it to use ipv4 and will listen on
that.
I did some research and it seems this is only on some *BSD systems
(netbsd, freebsd (version >= 5), openbsd) where IPV6_V6ONLY is set by
default.
I guess we just need something in the FAQ or Docs to specify this
behavior on those systems.
However if someone wanted to have it listen on both ipv6 and ipv4 I
guess they would have to run the server twice, one with
--listen-host=0.0.0.0 and one with it not set or --listen-host=::1 (or
whatever).
I tested on Linux Fedora Core 3, and it by default listened on both ipv6
and ipv4.
Thanks for the help.
Mark Phippard wrote:
>It seems like, if possible, it ought to just support both ipv6 and ipv4
>connections. If the goal were to control this with a switch, wouldn't the
>existing --listen-host=HOST switch do it? I would think if you have it the
>ipv4 address to bind to, that is what you would get.
>
>You might also look at this thread.
>
>http://subversion.tigris.org/servlets/BrowseList?list=dev&by=thread&from=296381
>
>Mark
>
>
>_____________________________________________________________________________
>Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
>_____________________________________________________________________________
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 25 06:51:43 2005