Hi Danny, I have tried with using "9.9.255.255" as broadcast ip address for cisco router, and linux machine acting as broadcastclient is able to sync with Cisco router [ Broadcast server ].
Then as you said the problem could be cisco using the all broadcast address. So could you please let me know how would you like to track the issue ? Thanks & Regards Ravikiran -----Original Message----- From: Danny Mayer [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 15, 2007 8:28 AM To: Ravikiran REDDY -X (ravikred - HCL at Cisco) Cc: [email protected] Subject: Re: [ntp:questions] configurations issue for broadcastclient in Linux machine Ravikiran REDDY -X (ravikred - HCL at Cisco) wrote: > Hello, > > Please clarify, > Linux machine when configured as broadcast client is not able to > create associations for the pkts received from the server [cisco > router] Am I missing anything here or should I need to have any > additional configuration in the ntp.conf file ? > > Server => cisco router with ntp image [ ip address 9.9.4.13 ] > Linux machine => broadcast client [ ip address 9.9.4.16 ] > [EMAIL PROTECTED] ntpv4]# uname -a > Linux nsstg-ntp-lnx 2.4.20-8 #1 Thu Mar 13 > 17:54:28 EST 2003 i686 i686 i386 GNU/Linux > [EMAIL PROTECTED] ntpv4]# > NTP version => ntpq> version > ntpq [EMAIL PROTECTED] Fri May 11 01:34:46 UTC > 2007 (1) > ntpq> > > --------ntp.conf file ----- > broadcastclient > driftfile /etc/ntp/drift > ---------------------------- > > > ----------- snippet from tcpdump on the Linux machine -------- > 00:58:55.882919 9.9.4.13.ntp > 255.255.255.255.ntp: v4 bcast strat 8 Do you know why it's insisting on sending the packet out to the 255.255.255.255 IP Address? Have you seen bug #629? https://ntp.isc.org/bugs/show_bug.cgi?id=629 The problem is that cisco seems to use the all broadcast address. I have discussed this with someone inside cisco but it looks like I will have to create a case for this situation. If I do so, you cannot do authentication on the received packets so you use at your own risk. This is because the packet gets received on the wildcard socket rather than the socket assigned for the purpose of receiving broadcast packets. We don't recommend this and I'm going to have to add configuration options to the config file to specify how to deal with this sort of thing. Danny _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
