Re: [PATCH v3] IPv6 timeserver for NTP

2015-10-28 Thread Naveen Singh
On Mon, Oct 26, 2015 at 12:46 AM, Patrik Flykt wrote: > On Fri, 2015-10-23 at 06:28 -0700, Naveen Singh wrote: > > > I didn't notice sin_port being used anywhere, so this is not needed? > > > > > This is being used in current code so I decided to follow the current

Re: [PATCH v3] IPv6 timeserver for NTP

2015-10-23 Thread Naveen Singh
Hi Patrik, Sorry for a very delayed reply on this thread. I do appreciate all your feedback and I would send you the revised patch on Monday after testing it for both IPv4 and IPv6 timeserver and all possible combinations. On Thu, Oct 8, 2015 at 5:22 AM, Patrik Flykt

Re: [PATCH v3] IPv6 timeserver for NTP

2015-10-08 Thread Patrik Flykt
Hi, On Tue, 2015-10-06 at 23:50 -0700, Naveen Singh wrote: > From: Naveen Singh > > Current NTP code is written with an assumption that timeserver is > always an IPv4 address. If there is an IPv6 timeserver then the socket > operation would fail with error as

[PATCH v3] IPv6 timeserver for NTP

2015-10-07 Thread Naveen Singh
From: Naveen Singh Current NTP code is written with an assumption that timeserver is always an IPv4 address. If there is an IPv6 timeserver then the socket operation would fail with error as Permission denied (13). This change in ntp.c ensures that code works fine with both

Re: [PATCH v3] IPv6 timeserver for NTP

2015-10-07 Thread Naveen Singh
On Tue, Oct 6, 2015 at 11:50 PM, Naveen Singh wrote: > From: Naveen Singh > > Current NTP code is written with an assumption that timeserver is > always an IPv4 address. If there is an IPv6 timeserver then the socket > operation would fail with