On Friday 22 May 2009 18:05:16 Jordi Espasa wrote:
Looks like you do not think at all. The reason was told to you, and
you didn't ever tried to do something. You prefer to think instead
of doing, aren't you?
I've fixed the commented conf error already, but it seems that the
FIRST warning
Hi all,
I've updated my public NTP server (time.cdmon.com); 4.5 works like a charm!
Despite of that, I see the following warning in /var/log/messages
(...]
May 21 23:53:53 time ntpd[12997]: sendto: Can't assign requested address
May 22 00:03:58 time last message repeated 66 times
May 22
On Fri, 22 May 2009 11:43:50 +0200, Jordi Espasa Clofent wrote:
Hi all,
I've updated my public NTP server (time.cdmon.com); 4.5 works like a charm!
Despite of that, I see the following warning in /var/log/messages
(...]
May 21 23:53:53 time ntpd[12997]: sendto: Can't assign requested address
Config file says?
# cat /etc/ntpd.conf
# $OpenBSD: ntpd.conf,v 1.9 2008/10/10 11:46:22 sthen Exp $
# sample ntpd configuration file, see ntpd.conf(5)
# Addresses to listen on (ntpd does not listen by default)
listen on *
# sync to a single server
server yes
server hora.roa.es
# use a random
On Fri, May 22, 2009 at 01:15:56PM +0200, Jordi Espasa Clofent wrote:
Config file says?
# cat /etc/ntpd.conf
# $OpenBSD: ntpd.conf,v 1.9 2008/10/10 11:46:22 sthen Exp $
# sample ntpd configuration file, see ntpd.conf(5)
# Addresses to listen on (ntpd does not listen by default)
listen on *
# sync to a single server
server yes
^^^ -- this seems to be wrong. Server line should contain
ipaddress/hostname, not 'yes'.
Yes, you've the reason; in /var/log messages:
(...)
May 22 09:13:54 time ntpd[31006]: 1 out of 2 peers valid
May 22 09:13:54 time
On Fri, May 22, 2009 at 11:43:50AM +0200, Jordi Espasa Clofent wrote:
Hi all,
I've updated my public NTP server (time.cdmon.com); 4.5 works like a charm!
Despite of that, I see the following warning in /var/log/messages
(...]
May 21 23:53:53 time ntpd[12997]: sendto: Can't assign requested
On Friday 22 May 2009 15:51:02 Jordi Espasa Clofent wrote:
# sync to a single server
server yes
^^^ -- this seems to be wrong. Server line should contain
ipaddress/hostname, not 'yes'.
Yes, you've the reason; in /var/log messages:
(...)
May 22 09:13:54 time
Jordi Espasa Clofent wrote:
# sync to a single server
server yes
server hora.roa.es
You shouldn't have this here like that.
server yes
The man(5) ntpd.conf if pretty clear on that.
server address [weight weight-value]
Specify the IP address or the hostname of an NTP server to syn-
Looks like you do not think at all. The reason was told to you, and you
didn't ever tried to do something. You prefer to think instead
of doing, aren't you?
I've fixed the commented conf error already, but it seems that the FIRST
warning I've commented in my INITIAL post is not related to
On Fri, May 22, 2009 at 10:05 AM, Jordi Espasa jordi.esp...@opengea.org wrote:
Looks like you do not think at all. The reason was told to you, and you
didn't ever tried to do something. You prefer to think instead of doing,
aren't you?
I've fixed the commented conf error already, but it seems
Hi folks,
Looking at /var/log/messages in my time server (OpenBSD 4.2, amd) I see
a lot of:
Mar 13 15:03:11 ntp01 ntpd[22179]: malformed packet received from
217.125.3.73
Mar 13 15:11:43 ntp01 ntpd[22179]: malformed packet received from
83.50.162.232
Mar 13 15:14:35 ntp01 ntpd[22179]:
On Mon, Mar 16, 2009 at 10:14:54AM +0100, Jordi Espasa Clofent wrote:
Hi folks,
Looking at /var/log/messages in my time server (OpenBSD 4.2, amd) I see
a lot of:
Mar 14 03:25:06 ntp01 ntpd[22179]: malformed packet received from
80.24.191.155
Looking at relationed code (ntp_msg.c and
It will serve time if it receives enough valid packets, possibly from
other sources. If you use the default setup, it uses multiple peers
so you should be ok.
Well, in this case, my box is the server (time.cdmon.com) and these kind
of packets are sendend by the ntp clients.
Btw, more recent
I can offer one interesting section from this site
http://www.openbsd.org/security.html :
OpenBSD 4.2 and earlier releases are not supported anymore. The
following paragraphs only list advisories issued while they were
maintained; these releases are likely to be affected by the advisories
for
15 matches
Mail list logo
