Dear Daniel,
Thank you for your reply and I'm sorry to be late.
-Only with IPv6, the Operating system handle the authentication.
What does this mean?
Sorry, let me explain about that in detail.
With IPv4, TSVN displays TSVN's authentication window.
With IPv6, however, TSVN displays Windows's authentication window(Windows
Security Window)
instead of TSVN's authentication window.
You should at least provide the error message you get, but there are
surely some more interesting details: How are your repos served,
svnadmin, httpd, SSH? The mention of serf implies httpd, so you could
provide some more details about if your are using proxys etc.
I'm so sorry. I'll show you the detail.
The error message is Valid name, no data record of requested type..
(http://support.microsoft.com/kb/819124/en) See WSANO_DATA (11004).
Both authenticated case and not authenticated case, TSVN doesn't work.
TSVN displays the same error message.
I could get the packets between the client and server.
It apparently seems the client can communicate with the server setting IPv6.
But there is no packet between the client and server on the way of
processing(when authenticating).
It's obviously hung up compared to IPv4's processing.
I think client can't control the communication with the server when
authenticating with IPv6.
[Client]
-TortoiseSVN 1.8.1
-Windows 7 Enterprise
-Use common company proxy server with SSL
-Authenticated with Active Directory Server(LDAP)
-Edit hosts file(Don't use DNS)
We registered the host name of NAT64 as SVN server.
-Use IPv6(Dual Stack)
[NAT64]
-convert IPv4(Client Side) to IPv6(Server Side)
-convert IPv6(Server Side) to IPv4(Client Side)
-Not exist the host name in DNS
-We can tell you more information if you need.
[SVN Server]
-RedHat 5.3
-Apache 2.2 setting of Active Directory(LDAP)
-Subversion 1.7.5
-Use only IPv4
[Active Directory]
-Use as LDAP Authentication
-Use only IPv6
-We can tell you more information if you need.
I'm none of the developers but from my understanding of IPv6 it
shouldn't have any influence on the authentication itself as this is
handled in layers above the addressing and communication.
With IPv6, TSVN doesn't display TSVN's authentication window.
I think that isn't caused by the addressing and communication but TSVN.
TSVN's developer said that's the SVN API or serf's issue.
Could you tell us if you know of that ?
Regards,
-Original Message-
From: Daniel Shahaf [mailto:danie...@apache.org]
Sent: Thursday, August 08, 2013 10:56 PM
To: Okabayashi, Hirotsugu
Cc: users@subversion.apache.org
Subject: Re: Cope with IPv6
Forwarding Thorsten's answer to the OP.
Thorsten Schöning wrote on Mon, Aug 05, 2013 at 09:58:20 +0200:
Guten Tag Okabayashi, Hirotsugu,
am Montag, 5. August 2013 um 09:17 schrieben Sie:
-Only with IPv6, the Operating system handle the authentication.
What does this mean?
So, both authenticated case and not authenticated case,
TSVN doesn't work. TSVN display the same error message.
You should at least provide the error message you get, but there are
surely some more interesting details: How are your repos served,
svnadmin, httpd, SSH? The mention of serf implies httpd, so you could
provide some more details about if your are using proxys etc.
I'm none of the developers but from my understanding of IPv6 it
shouldn't have any influence on the authentication itself as this is
handled in layers above the addressing and communication.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...05151- 9468- 55
Fax...05151- 9468- 88
Mobil..0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG
Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
