Invalid argument...

Vernon Schryver vjs@calcite.rhyolite.com
Tue Nov 30 02:57:48 UTC 2004


> From: "Evert Meulie" 

> Here's a short except from my syslog:
> Nov 30 00:08:29 sb62g2 dccd[9766]: sendto(OK, client 1 at 195.146.155.55,0: Invalid argument
> Nov 30 00:08:30 sb62g2 dccd[9766]: sendto(OK, client 1 at 195.146.155.55,0: Invalid argument
> Nov 30 00:11:25 sb62g2 dccd[9766]: sendto(OK, client 1 at 209.79.207.1,0: Invalid argument
> Nov 30 00:11:25 sb62g2 dccd[9766]: sendto(OK, client 1 at 209.79.207.1,0: Invalid argument
>
> How do I fix/prevent these?

Dccd was told EINVAL by your flavor of UNIX when dccd tried to answer
requests from those IP addresses.

The reason for the EINVAL rejection from the UNIX kernel is hard to
know, but those port numbers of "0" look suspicious.  They could be
caused by a bug in dccd, a bug in your flavor of UNIX, some kind of
too smart by half NAT box doing broken port mapping, or something else.

How often do you see those error messages?
Do they happen with any other IP addresses?
Does anyone else see them?  (I don't see them z.dcc-servers.net log)


Another possibility is that your flavor of UNIX answers EINVAL for
sendto() when the destination address is unreachable, and the "0" port
numbers are merely a bug in the error message formatting in dccd.


Vernon Schryver    vjs@rhyolite.com



More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.