[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Cope with IPv6

From: Okabayashi, Hirotsugu <Hirotsugu.Okabayashi_at_jp.sony.com>
Date: Wed, 31 Jul 2013 17:52:45 +0900

Dear User Support,

We tested the IPv6 communication of TortiseSVN.
We confirm there is no problem the communication of Native IPv6.

See the attached file.
That is our environment.
We can get the real server's FQDN(can access), but can't see the data
(with the error message like "A kind of the requested data can't be found.")
Let me confirm TortiseSVN's specification.
1. Tortoise can connect in the only peer2peer?
2. Subversion server also requires the setting of IPv6 in case of the
   communication of IPv6 between TortiseSVN and the server(NAT64)?
   (Can Subversion server throw the packets with TortiseSVN directly?)

I think many companies use NAT64 for IPv6 problem.
Please cooperate to cope with IPv6.
You also can take advantage to test about IPv6 with us.

Regards,

> -----Original Message-----
> From: Okabayashi, Hirotsugu
> Sent: Friday, July 12, 2013 10:49 AM
> To: Okabayashi, Hirotsugu; Stefan Küng
> Cc: users; SGS/systemtec/CMsupport
> Subject: RE: Cope with IPv6
>
> Dear User Support,
>
> Could you give us more information?
> We tried to test with an IPv6.
> We found the 2 points about the TortoiseSVN's specification.
> - TortoiseSVN can connect to SVN server with a native IPv6.(directly)
> - TortoiseSVN can't connect to SVN server via NAT64(router) server with
> a IPv6
> * TortoiseSVN-NAT64 uses a IPv6 and NAT64-SVN server uses a IPv4.
>
> Are those correct TortoiseSVN's specification ?
>
> Regards,
>
> > -----Original Message-----
> > From: Okabayashi, Hirotsugu
> > Sent: Friday, June 21, 2013 9:32 AM
> > To: Stefan Küng
> > Cc: users; SGS/systemtec/CMsupport
> > Subject: RE: Cope with IPv6
> >
> > Dear Stefan
> >
> > Thank you for your help.
> > I got that.
> >
> > >Such a test takes about 10 minutes...
> > First of all, we want to know the specification because we don't have
> > any testing environment and must cope with an IPv6 in the future.
> >
> > I really appreciate it.
> >
> > Regards,
> >
> > -----Original Message-----
> > From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> > Sent: Friday, June 21, 2013 2:40 AM
> > To: Okabayashi, Hirotsugu
> > Cc: users; SGS/systemtec/CMsupport
> > Subject: Re: Cope with IPv6
> >
> > On 20.06.2013 03:11, Okabayashi, Hirotsugu wrote:
> > > Dear User Support
> > >
> > > Thank you for your advice.
> > >> However, if your SVNServer is only accessible via an IPv6 address
> > >> and can't be accessed with an IPv4 address, then you need to use a
> > >> nightly build of TortoiseSVN. Only the nightly builds are compiled
> > >> with
> > IPv6 support enabled.
> >
> > > You mean the official release doesn't support the dual
> > > stack(IPv6/IPv4)
> > implementation ?
> >
> > The official release does support dual stack implementation, as long
> > as the server is reachable via IPv4.
> > Only if the server can not be reached via IPv4 but only via IPv6 you
> > need a nightly build.
> >
> > > Can we recognize we can select either an IPv4 or IPv6 ?(About the
> > > official release) Only if we use the a nightly build, we can use the
> > > dual
> > stack(IPv6/IPv4) implementation.
> > > Is that right ?
> >
> > I suggest you download the official release and try. If it doesn't
> > work, try a nightly build.
> >
> > Such a test takes about 10 minutes...
> >
> > Stefan
> >
> > --
> > ___
> > oo // \\ "De Chelonian Mobile"
> > (_,\/ \_/ \ TortoiseSVN
> > \ \_/_\_/> The coolest interface to (Sub)version control
> > /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3061722

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

test_environment.png
Received on 2013-07-31 10:52:58 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.