Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Mike Stump
In article <587e34f2.6400...@news.eternal-september.org>, Robert Scott wrote: >Perhaps the problem is with my understanding of socket coding. I >found "time-d.nist.gov" that is supposed to have an IPv6 address of >2610:20:6F15:15::27, but when I get its address info, it

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Doug McIntyre
no-one@notreal.invalid (Robert Scott) writes: >Perhaps the problem is with my understanding of socket coding. I >found "time-d.nist.gov" that is supposed to have an IPv6 address of >2610:20:6F15:15::27, but when I get its address info, it always says >IPv4, 129:6:15:27. I see the 15 and 27, so

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Brian Inglis
On 2017-01-17 08:25, Robert Scott wrote: > Perhaps the problem is with my understanding of socket coding. I > found "time-d.nist.gov" that is supposed to have an IPv6 address of > 2610:20:6F15:15::27, but when I get its address info, it always says > IPv4, 129:6:15:27. I see the 15 and 27, so

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Jakob Bohm
On 17/01/2017 18:21, Robert Scott wrote: On Tue, 17 Jan 2017 17:21:43 +0100, Jakob Bohm wrote: For testing, set up your own server on your own (virtual) machine. Then you can completely control what it's address settings and DNS entries are, and you also avoid sending

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Robert Scott
On Tue, 17 Jan 2017 17:21:43 +0100, Jakob Bohm wrote: > >For testing, set up your own server on your own (virtual) machine. > >Then you can completely control what it's address settings and DNS >entries are, and you also avoid sending junk or overload traffic to >someone

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Jakob Bohm
On 17/01/2017 16:25, Robert Scott wrote: Perhaps the problem is with my understanding of socket coding. I found "time-d.nist.gov" that is supposed to have an IPv6 address of 2610:20:6F15:15::27, but when I get its address info, it always says IPv4, 129:6:15:27. I see the 15 and 27, so there is

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Dan Geist
Robert, that host doesn't look to have a v6 record: [dan@shell ~]$ host time-d.nist.gov time-d.nist.gov has address 129.6.15.27 Obviously, you're getting the ipv4 address correctly, though. Here's a good primer on IPv6 application porting:

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Robert Scott
Perhaps the problem is with my understanding of socket coding. I found "time-d.nist.gov" that is supposed to have an IPv6 address of 2610:20:6F15:15::27, but when I get its address info, it always says IPv4, 129:6:15:27. I see the 15 and 27, so there is some translation going on that I don't

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Paul
The proximate cause is using the wrong name for the pool. 2.pool.ntp.org will return IPv6. Use one of those. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Testing IPv6 code

2017-01-17 Thread Kiss Gábor
> IPv4 addresses. Is there a server I can access that ONLY responds > with IPv6 so I can force my code to go there? Set up your own firewall to make IPv4 address of a choosen server unreachable. Gabor ___ questions mailing list questions@lists.ntp.org

[ntp:questions] Testing IPv6 code

2017-01-17 Thread Robert Scott
I am developing code that I hope will work with both IPv4 and IPv6, and it does seem to work with IPv4. But how can I test my IPv6 code? I have been using "ntp.pool.org", which only delivers IPv4 addresses, as far as I can tell. I tried "2.ntp.pool.org" and all I get are more IPv4 addresses. Is