Right... I installed a second service with the '-6' option. This did not
make any difference.
Doing more wireshark sniffing:
- At first, SVN client tries connecting from the local-link IPv6 address.
There is no response. Two TCP retransmissions fail as well.
- Second, SVN client tries connecting from the temporary IPv6 address. There
is no response. Two TCP retransmissions fail as well.
- Finally, SVN client falls back to IPv4. This is successful.
The other client PC (Win10 Home 1803) runs an older SVN client (v1.9.7), and
does not try IPv6 first; this one goes straight to IPv4. Running the 'svn
info' command from that older version on my own PC also goes straight to
IPv4.
I believe there is no option to force the client to use IPv4?? (except
specifically entering the IPv4 IP address)
Have I found a bug?
-----Original Message-----
From: Stefan Sperling [mailto:stsp_at_elego.de]
Sent: Tuesday 5 June 2018 12:12
To: Johannes van der Vegt <Johannes.van.der.Vegt_at_applicos.com>
Cc: users_at_subversion.apache.org
Subject: Re: SVN access became slow
On Tue, Jun 05, 2018 at 10:16:15AM +0200, Johannes van der Vegt wrote:
> Hi group,
>
>
>
> Suddenly SVN access became very slow on my PC. Before, everything ran
fine.
>
>
>
> We have a small company network.
>
> * "Server" PC: Win10 Pro (1709), runs the svnserve.exe service,
> version 1.10.0
> * My PC: Win10Pro (1803), using SVN 1.10.0-dev (Apr 14, 2018)
> * Other PC: Win10Pro (1803)
>
>
>
> When I run "svn info svn://server/RepoPath", I need to wait very long
> (over
> 40 seconds) before I get the response.
>
> When I use the server's specific IPv4 address, it responds immediately.
>
> When I use the server's specific IPv6 address, I get errors:
svnserve supports either IPv4 or IPv6, but not both at the same time.
You could run two svnserve processes, one for IPv4 and one for IPv6.
There is a '--prefer-ipv6' option which makes svnserve use IPv6 instead of
IPv4, see the output 'svnserve --help'.
Received on 2018-06-05 14:54:29 CEST