You might start by updating the framework’s Cluster class accept a hostname that would be used for both Locator and Server classes. Then in an IPv6 tests you could set the hostname to '0:0:0:0:0:0:0:1’, which is the loopback address. In theory this should work.
In Cluster.hpp: Look for all the NamedType definitions and add. using BindAddress = NamedType<std::string, struct BindAddressParameter>; Plumb it though to Locator and Server. In your test: Cluster cluster(…, BindAddress(“0:0:0:0:0:0:0:1")); Even more simple may be to not allow the hostname but just a flag for IPv4 or IPv6 and internally set the hostname to the IPv6 or IPv6 localhost address. In Cluster.hpp: using UseIpv6 = NamedType<std::bool, struct UseIpv6Parameter>; Then plumb that through to Locator and Server and select the appropriate loopback address. In your test: Cluster cluster(…, UseIpv6(true)); I can help you in more detail if you want. -Jake > On Aug 21, 2019, at 12:34 AM, Mario Ivanac <mario.iva...@est.tech> wrote: > > Hi, > > > Can you help me, how to simulate ipv6 in new integration test framework? > > > BR, > > Mario > > ________________________________ > Šalje: Jacob Barrett <jbarr...@pivotal.io> > Poslano: 14. kolovoza 2019. 21:00:35 > Prima: dev@geode.apache.org <dev@geode.apache.org> > Predmet: Re: geode-native ipv6 > > Can you build an integration test in the new framework? > >> On Aug 14, 2019, at 11:25 AM, Mario Ivanac <mario.iva...@est.tech> wrote: >> >> Hi, >> >> >> created https://issues.apache.org/jira/browse/GEODE-7086, and PR with code >> impacts. >> >> Proposed solution was tried on IPv6 environment, and basic operations >> (PUT/GET) were successful. >> >> Additional test needed. >> >> >> BR, >> >> Mario >> >> ________________________________ >> Šalje: Blake Bender <bben...@pivotal.io> >> Poslano: 9. kolovoza 2019. 0:03:32 >> Prima: dev@geode.apache.org <dev@geode.apache.org> >> Predmet: Re: geode-native ipv6 >> >> This chunk of code in the client handshake code leads me to believe it is >> still IPv4 only. Won't say it's definitive, cause I'm not 100% certain >> hostaddr is used on the server side, but still... >> >> // writing first 4 bytes of the address. This will be same until >> // IPV6 support is added in the client >> uint32_t temp; >> memcpy(&temp, hostAddr, 4); >> m_memID.writeInt(static_cast<int32_t>(temp)); >> >> >>> On Thu, Aug 8, 2019 at 1:18 PM Jacob Barrett <jbarr...@pivotal.io> wrote: >>> >>> We are on the latest ACE. >>> >>>> On Aug 8, 2019, at 9:56 AM, Mark Hanson <mhan...@pivotal.io> wrote: >>>> >>>> The latest ACE framework seems to have support, but I don’t know how far >>> off latest we are. I don’t think we test anything in an IPv6 context, so I >>> would say no that we don’t officially support it in the client. Given some >>> time, I could do some testing.. >>>> >>>> Thanks, >>>> Mark >>>> >>>>> On Aug 8, 2019, at 7:35 AM, Blake Bender <bben...@pivotal.io> wrote: >>>>> >>>>> I'm sure someone will chime in with a more definitive answer, but I'm >>>>> pretty certain the answer is no, sorry. >>>>> >>>>> Thanks, >>>>> >>>>> Blake >>>>> >>>>> >>>>>> On Thu, Aug 8, 2019 at 4:28 AM Mario Ivanac <mario.iva...@est.tech> >>> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> can you tell me does geode-native client support ipv6? >>>>>> >>>>>> >>>>>> BR, >>>>>> >>>>>> Mario >>>>>> >>>> >>>
