bad client-ID 0 from 151.201.243.129

Those who are running public DCC servers might want to use
`route add 151.201.243.129 127.0.0.1` to defend against the hundreds
of bogus DCC client messages coming from 151.201.243.129.

I've examined the source for an explanation and tried to convince
the DCC client library code to accept a client-ID 0, but failed.
That and the fact that the messages come fron monly 151.201.243.129
lead me to believe that the cause is at best an ill considered
change to the source.


Vernon Schryver    vjs@rhyolite.com