You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Okabayashi, Hirotsugu" <Hi...@jp.sony.com> on 2013/08/05 09:17:39 UTC
Cope with IPv6
Dear User Support,
Could you tell us the specifications about the authentication with IPv6 ?
These behavior bothers us about IPv6.
-When connecting to SVN server with IPv6, the client tool(TortoiseSVN:TSVN) can't handle the authentication operation.
-Only with IPv6, the Operating system handle the authentication. So, both authenticated case and not authenticated case,
TSVN doesn't work. TSVN display the same error message.
At first, we thought the problem causes TSVN's specification.
But, the TSVN's user support said the authentication is handled by the SVN's API and the serf library.
So, they said the problem relates to SVN's API and the serf library's specification.
With IPv6, do SVN's API and the serf library work well when authenticating?
Regards,
******************************************
Sony Global Solutions Inc.
Hirotsugu Okabayashi
Tel: 03-5479-6566
Mail:<Hi...@jp.sony.com>
******************************************
RE: Cope with IPv6
Posted by "Okabayashi, Hirotsugu" <Hi...@jp.sony.com>.
Dear Ivan Zhakov,
Thank you very much.
> -----Original Message-----
> From: Ivan Zhakov [mailto:ivan@visualsvn.com]
> Sent: Tuesday, August 13, 2013 8:52 PM
> To: Okabayashi, Hirotsugu
> Cc: Daniel Shahaf; users@subversion.apache.org
> Subject: Re: Cope with IPv6
>
> On Tue, Aug 13, 2013 at 12:52 PM, Okabayashi, Hirotsugu
> <Hi...@jp.sony.com> wrote:
> > 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.
> TSVN displays Windows's authentication window when it tries to get list
> of repositories using Windows API, not Subversion libraries.
>
>
>
>
> --
> Ivan Zhakov
> CTO | VisualSVN | http://www.visualsvn.com
Re: Cope with IPv6
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Tue, Aug 13, 2013 at 12:52 PM, Okabayashi, Hirotsugu
<Hi...@jp.sony.com> wrote:
> 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.
TSVN displays Windows's authentication window when it tries to get
list of repositories using Windows API, not Subversion libraries.
--
Ivan Zhakov
CTO | VisualSVN | http://www.visualsvn.com
Re: Cope with IPv6
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Okabayashi, Hirotsugu,
am Dienstag, 13. August 2013 um 10:52 schrieben Sie:
> [Client]
[...]
> -Edit hosts file(Don't use DNS)
> We registered the host name of NAT64 as SVN server.
What does this mean? You can only map IP addresses to host names in
this file. Does the host name of NAT64 map to the IP address of your
SVN server or does NAT64 host name map to IP address of NAT64 host and
you're accessing NAT64 as SVN server in Tortoise? Please post the
relevant line in hosts file and the URL you use in Tortoise to access
your repo with explanation of which host name resolves to which IP.
Why should that be necessary in general? Your SVN server is IPv4 only,
why should the IPv4 capable Windows 7 should access it using NAT64?
If you want to use IPv6 with your Windows 7, make you SVN server
available using IPv6. I don't understand what's the purpose of NAT64
in your scenario as "the server side" is SVN Server and is not capable
of IPv6. Does your NAT64 translate IPv4 from Windows 7 to IPv6
internally, just to translate it back to IPv4 again externally to
communicate with SVN Server?
It would only make sense to use NAT64 to translate between your SVN
server and AD, because Windows 7 can communicate with AD directly
using IPv6, but SVN Server can't. Therefore I would suggest changing
your hosts file on the Windows 7 client to remove whatever you map to
NAT64 and let SVN Server and Windows Client communicate directly.
Afterwards you need to make SVN Server IPv6 aware or AD IPv4 or both
simply dual stack, which would be what I would do in your case as dual
stack is and will be common and standard for years. NAT64 seems to
only complicating things unnecessarily.
From your description I don't think there's something wrong with
Tortoise or Subversion, but with your network. But my experience with
IPv6 is limited...
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@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
RE: Cope with IPv6
Posted by "Okabayashi, Hirotsugu" <Hi...@jp.sony.com>.
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:danielsh@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.Schoening@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
> >
Re: Cope with IPv6
Posted by Daniel Shahaf <da...@apache.org>.
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.Schoening@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
>
Re: Cope with IPv6
Posted by Thorsten Schöning <ts...@am-soft.de>.
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.Schoening@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
RE: Cope with IPv6
Posted by "Okabayashi, Hirotsugu" <Hi...@jp.sony.com>.
Dear User Support,
Is there a problem about the inquiry way ? We would appreciate it if you could help us.
Could you tell us the specifications about the authentication with IPv6 ?
[Subversion] 1.7.5
[TortoiseSVN]1.8.1
These behavior bothers us about IPv6.
-When connecting to SVN server with IPv6, the client tool(TortoiseSVN:TSVN) can't handle the authentication operation.
The behavior with IPv4 is OK.
-Only with IPv6, the operating system can handle the authentication.(TSVN can't handle it.) So, both authenticated case and
not authenticated case, TSVN doesn't work. TSVN display the same error messages. I guess TSVN lose its operation.
At first, we thought the problem causes TSVN's specification.
But, the TSVN's user support team said the authentication is handled by the SVN's API and the serf library.
So, they said the problem relates to SVN's API and the serf library's specification.
With IPv6, do SVN's API and the serf library work well when authenticating?
Regards,
******************************************
Sony Global Solutions Inc.
Hirotsugu Okabayashi
Tel: 03-5479-6566
Mail:<Hi...@jp.sony.com>
******************************************
> -----Original Message-----
> From: Okabayashi, Hirotsugu
> Sent: Tuesday, August 06, 2013 8:55 AM
> To: users@subversion.apache.org
> Cc: SGS/systemtec/CMsupport
> Subject: Cope with IPv6
>
> Dear User Support,
>
> Sorry to mistake. This is correct.
>
> Could you tell us the specifications about the authentication with IPv6 ?
> These behavior bothers us about IPv6.
> -When connecting to SVN server with IPv6, the client
> tool(TortoiseSVN:TSVN) can't handle the authentication operation.
> -Only with IPv6, the operating system can't handle the authentication.
> So, both authenticated case and not authenticated case,
> TSVN doesn't work. TSVN display the same error messages.
>
> At first, we thought the problem causes TSVN's specification.
> But, the TSVN's user support said the authentication is handled by the SVN's
> API and the serf library.
> So, they said the problem relates to SVN's API and the serf library's
> specification.
>
> With IPv6, do SVN's API and the serf library work well when authenticating?
>
> Regards,
>
> > -----Original Message-----
> > From: Okabayashi, Hirotsugu
> > Sent: Monday, August 05, 2013 4:18 PM
> > To: users@subversion.apache.org
> > Cc: SGS/systemtec/CMsupport
> > Subject: Cope with IPv6
> >
> > Dear User Support,
> >
> > Could you tell us the specifications about the authentication with IPv6 ?
> > These behavior bothers us about IPv6.
> > -When connecting to SVN server with IPv6, the client
> > tool(TortoiseSVN:TSVN) can't handle the authentication operation.
> > -Only with IPv6, the Operating system handle the authentication. So,
> > both authenticated case and not authenticated case,
> > TSVN doesn't work. TSVN display the same error message.
> >
> > At first, we thought the problem causes TSVN's specification.
> > But, the TSVN's user support said the authentication is handled by the
> > SVN's API and the serf library.
> > So, they said the problem relates to SVN's API and the serf library's
> > specification.
> >
> > With IPv6, do SVN's API and the serf library work well when authenticating?
> >
> > Regards,
> >
> > ******************************************
> > Sony Global Solutions Inc.
> > Hirotsugu Okabayashi
> > Tel: 03-5479-6566
> > Mail:<Hi...@jp.sony.com>
> > ******************************************
Re: Cope with IPv6
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Okabayashi, Hirotsugu,
am Dienstag, 6. August 2013 um 01:54 schrieben Sie:
> Sorry to mistake. This is correct.
You should really NOT create new threads for an already mentioned
problem without providing any more details. Please stay on one thread
only.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@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
Cope with IPv6
Posted by "Okabayashi, Hirotsugu" <Hi...@jp.sony.com>.
Dear User Support,
Sorry to mistake. This is correct.
Could you tell us the specifications about the authentication with IPv6 ?
These behavior bothers us about IPv6.
-When connecting to SVN server with IPv6, the client tool(TortoiseSVN:TSVN) can't handle the authentication operation.
-Only with IPv6, the operating system can't handle the authentication. So, both authenticated case and not authenticated case,
TSVN doesn't work. TSVN display the same error messages.
At first, we thought the problem causes TSVN's specification.
But, the TSVN's user support said the authentication is handled by the SVN's API and the serf library.
So, they said the problem relates to SVN's API and the serf library's specification.
With IPv6, do SVN's API and the serf library work well when authenticating?
Regards,
> -----Original Message-----
> From: Okabayashi, Hirotsugu
> Sent: Monday, August 05, 2013 4:18 PM
> To: users@subversion.apache.org
> Cc: SGS/systemtec/CMsupport
> Subject: Cope with IPv6
>
> Dear User Support,
>
> Could you tell us the specifications about the authentication with IPv6 ?
> These behavior bothers us about IPv6.
> -When connecting to SVN server with IPv6, the client
> tool(TortoiseSVN:TSVN) can't handle the authentication operation.
> -Only with IPv6, the Operating system handle the authentication. So, both
> authenticated case and not authenticated case,
> TSVN doesn't work. TSVN display the same error message.
>
> At first, we thought the problem causes TSVN's specification.
> But, the TSVN's user support said the authentication is handled by the SVN's
> API and the serf library.
> So, they said the problem relates to SVN's API and the serf library's
> specification.
>
> With IPv6, do SVN's API and the serf library work well when authenticating?
>
> Regards,
>
> ******************************************
> Sony Global Solutions Inc.
> Hirotsugu Okabayashi
> Tel: 03-5479-6566
> Mail:<Hi...@jp.sony.com>
> ******************************************