...@ntp.org wrote:
On 12/7/2011 11:15 PM, rakesh v wrote:
Thanks for your inputs Danny.
Hi Dave,
Can you give your inputs on this below issue?
Is the socket bind failing due to the reuse of the udp port 123. But I
assume for ntp multicast client also we use the same port for listening
being received on client
side in wireshark. Packets are not received.
Here Iam not sure why the socket bind is failing for ntpd? Any inputs on
this?
Regs,
RV.
On Wed, Dec 7, 2011 at 8:54 AM, Danny Mayer ma...@ntp.org wrote:
On 11/30/2011 3:50 AM, rakesh v wrote:
Hi,
Iam facing issues
Hi Danny,
Thanks for your valuable reply. Please see my comments/observations inlined
On Wed, Dec 7, 2011 at 8:54 AM, Danny Mayer ma...@ntp.org wrote:
On 11/30/2011 3:50 AM, rakesh v wrote:
Hi,
Iam facing issues with ntp broadcast ip address in case of IPv6.
Iam using the latest ntp
run ntp multicast client in
Openntp/SNTP? Is there any alternative?
On Wed, Dec 7, 2011 at 11:35 AM, David Woolley
david@ex.djwhome.demon.invalid wrote:
rakesh v wrote:
*RV: I couldn't run the ntpd with -D2 option as it is not available.*
*These are the options available for ntpd
in the client but time
synchronization does not happen in the client.
I have even enabled the authentication on both the sides also. But no use.
Can somebody help me out from this?
--
Thanks Regs,
Rakesh V
___
questions mailing list
questions@lists.ntp.org
http
