All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Koski <david@KosmosIsland.com>
To: lartc@vger.kernel.org
Subject: [LARTC] long delays with NNTP after switching T1 to other servcie provider
Date: Sat, 13 Apr 2002 15:31:20 +0000	[thread overview]
Message-ID: <marc-lartc-101871203324978@msgid-missing> (raw)

After moving a Linux server serving as a wireless gateway/router to another ISP,
I noticed a problem with NNTP.  When attempting to communicate NNTP through the
Linux server, there are long delays that often result in timeouts.  For example,
when using the newsreader pan, I get the following errors in the log file, in
reverse chronological order:

Connect Failure
NNTP handshake failed: Error reading from socket.
Handshake failed: Error reading from socket.
NNTP handshake failed: Error reading from socket.
Timed out waiting to read from the server.


The Linux server is fed with a T1 from a different source.  Before changing
over, there was no problem with NNTP.  The only other difference that would seem
to matter is the reconfiguration of the server.  I only took some services off
line (qmail for example) and reconfigured the routing.  All other traffic
through the server works well, with the exception of dhcp which I haven't
resolved yet.

I suspect a QoS control issue from upstream.  Is it possible that NNTP requests
are sitting in a queue somewhere waiting for a the "right" time to dequeue?  If
so, would there be something I could do with the TOS that might help?  Or Am I
on the wrong track?

TIA,
David Koski
david@KosmosIsland.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-04-13 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 15:31 David Koski [this message]
2002-04-13 17:51 ` [LARTC] long delays with NNTP after switching T1 to other ser Greg Scott
2002-04-14  6:29 ` Greg Scott

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=marc-lartc-101871203324978@msgid-missing \
    --to=david@kosmosisland.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.