I have a RH System at home, no mods, right out of the box.
It keeps sending UDP packets to 63.240.115.23.codaauth, so fast
it's killing my PPP bandwidth.
Anybody know how to shut it up? There is no coda file-system on
that machine (that I know of).
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
On Fri, 9 Jan 2004, Richard B. Johnson wrote:
> I have a RH System at home, no mods, right out of the box.
> It keeps sending UDP packets to 63.240.115.23.codaauth, so fast
> it's killing my PPP bandwidth.
>
> Anybody know how to shut it up? There is no coda file-system on
> that machine (that I know of).
Figure out what program is sending the packets.
Chances are your bind got rooted. Guess why newer
RH distros have some kind of a firewall up by default?
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
On Fri, Jan 09, 2004 at 07:33:49AM -0500, Richard B. Johnson wrote:
> I have a RH System at home, no mods, right out of the box.
> It keeps sending UDP packets to 63.240.115.23.codaauth, so fast
> it's killing my PPP bandwidth.
Codaauth2 is the IANA port for the Coda authentication daemon.
In any normal Coda environment, only the 'clog' command sends any data
to this port. It is started by the user when that user wants to get a
new token for the next 25 hours, and gives up after couple of retries
(about 30 seconds?) when it doesn't get a reply.
Network impact should be pretty much insignificant, here is a tcpdump of
a successful connection,
16:58:19.226110 client.34702 > server.codaauth2: udp 301 (DF)
16:58:19.249315 server.codaauth2 > client.34702: udp 80
16:58:19.249530 client.34702 > server.codaauth2: udp 76 (DF)
16:58:19.250009 server.codaauth2 > client.34702: udp 84
16:58:19.250300 client.34702 > server.codaauth2: udp 60 (DF)
16:58:19.250855 server.codaauth2 > client.34702: udp 140
16:58:19.251073 client.34702 > server.codaauth2: udp 60 (DF)
16:58:19.251503 server.codaauth2 > client.34702: udp 60
And here is a tcpdump of a failing handshake (i.e. no replies from the
codauth2 server).
17:00:54.047567 client.34703 > server.codaauth2: udp 301 (DF)
17:00:54.348124 client.34703 > server.codaauth2: udp 301 (DF)
17:00:54.649048 client.34703 > server.codaauth2: udp 301 (DF)
17:00:55.121980 client.34703 > server.codaauth2: udp 301 (DF)
17:00:56.067797 client.34703 > server.codaauth2: udp 301 (DF)
17:00:57.958431 client.34703 > server.codaauth2: udp 301 (DF)
17:01:01.738718 client.34703 > server.codaauth2: udp 301 (DF)
As you can see, we never retransmit withing 300ms and are backing off on
each successive try. If something is hogging your PPP connection, I
don't think it is Coda related. I run Coda over dialup pretty often
myself.
Jan