From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: What is codaauth? Why is Linux polling it?
Date: Tue, 13 Jan 2004 17:09:51 -0500 [thread overview]
Message-ID: <20040113220950.GA12308@delft.aura.cs.cmu.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0401082135560.1311@chaos>
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
prev parent reply other threads:[~2004-01-13 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 12:33 Richard B. Johnson
2004-01-11 3:58 ` Rik van Riel
2004-01-13 22:09 ` Jan Harkes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040113220950.GA12308@delft.aura.cs.cmu.edu \
--to=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®