Re: ntpd sendto: Can't assign requested address

2013-02-12 Thread Stefan Sieg

Am 2012-01-13 18:42, schrieb fe...@banane.de.vc:

Hello,

I run OpenBSD 5.0 (amd64) with ntpd. About 5 to 10 times a day, it
logs errors like the following to /var/log/messages and
/var/log/daemon:

Jan 11 02:04:53 abc ntpd[26588]: sendto: Can't assign requested 
address


/etc/ntpd.conf:
listen on *
server ptbtime2.ptb.de
server ptbtime3.ptb.de

This box is part of the ntp pool (www.pool.ntp.org) so it gets about
10 ntp querys per second on average, occasionally many more.

What to do?
Thanks
feily


Hello, (one year later:)

on my poolserver i saw this message 50+ per hour.
Today i found that they were caused by clients connecting with
source port 0. I don't think that this are valid connections,
after blocking them with pf the ntpd warnings are gone.

Greetings
Stefan



Re: ntpd sendto: Can't assign requested address

2013-02-12 Thread Stuart Henderson
On 2013-02-10, Stefan Sieg stefan.s...@gmx.de wrote:
 on my poolserver i saw this message 50+ per hour.
 Today i found that they were caused by clients connecting with
 source port 0. I don't think that this are valid connections,
 after blocking them with pf the ntpd warnings are gone.

IIRC old versions of firewall/1 will protect you from this by 
crashing :-)

They are probably from crappy IP stacks on embedded systems
(routers etc). Port 0 is reserved and shouldn't be used.



Re: ntpd sendto: Can't assign requested address

2012-01-13 Thread Henning Brauer
* fe...@banane.de.vc fe...@banane.de.vc [2012-01-13 18:43]:
 I run OpenBSD 5.0 (amd64) with ntpd. About 5 to 10 times a day, it
 logs errors like the following to /var/log/messages and
 /var/log/daemon:
 
 Jan 11 02:04:53 abc ntpd[26588]: sendto: Can't assign requested address

that's sendto(2) returning EADDRNOTAVAIL.
without having checked wether that actually is the error returned in
this case...

 This box is part of the ntp pool (www.pool.ntp.org) so it gets about
 10 ntp querys per second on average, occasionally many more.

..but could you simply run out of port space? if so, playing with
sysctl net.inet.ip.port* should help. 

-- 
Henning Brauer, h...@bsws.de, henn...@openbsd.org
BS Web Services, http://bsws.de, Full-Service ISP
Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed
Henning Brauer Consulting, http://henningbrauer.com/