Re: [chrony-users] How to set chrony on a remote server with always on internet

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Mon, Apr 05, 2010 at 08:36:34AM +0530, J. Bakshi wrote:
> Thanks for your response.  I have followed the tcpdump method with both
> firewall enable and disable mode and both the time the output is same; like
> 
> ``````````````````````
> 08:32:53.163760 IP 192.168.1.1.44835 > localhost.323: UDP, length 40
> 08:32:53.163853 IP 192.168.1.1.323 > 192.168.1.1.44835: UDP, length 44
> 08:32:53.164063 IP 192.168.1.1.44835 > localhost.323: UDP, length 40
> 08:32:53.164082 IP 192.168.1.1.323 > 192.168.1.1.44835: UDP, length 44
> 08:32:53.164167 IP 192.168.1.1.44835 > localhost.323: UDP, length 40
> 08:32:53.164184 IP 192.168.1.1.323 > 192.168.1.1.44835: UDP, length 44
> 08:32:53.164231 IP 192.168.1.1.44835 > localhost.323: UDP, length 40
> 08:32:53.164247 IP 192.168.1.1.323 > 192.168.1.1.44835: UDP, length 44
> 08:32:53.164293 IP 192.168.1.1.44835 > localhost.323: UDP, length 40
> 08:32:53.164309 IP 192.168.1.1.323 > 192.168.1.1.44835: UDP, length 44
> ````````````````````````````
> you can see here that port 323 is accessible but still I get the error as
> 
> ````````````
>  chronyc> tracking
> 506 Cannot talk to daemon
> `````````````````

I think the problem here is that the responses come from different
address than the request was sent to, localhost (which I presume is
127.0.0.1) is different from 192.168.1.1.

This would suggest a problem in network configuration. Both chronyc
and chronyd bind to 0.0.0.0 by default, so it's up to kernel to do
the right thing.

Adding "bindcmdaddress 127.0.0.1" to chrony.conf might force
chronyd to reply from 127.0.0.1.

-- 
Miroslav Lichvar

---
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.