All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Hemingway <matt@supplyedge.com>
To: Jamie Harris <jamie@jharris.homeip.net>
Cc: linux-admin@vger.kernel.org
Subject: Re: Port 25 Delay
Date: Thu, 17 Jul 2003 11:17:50 -0700	[thread overview]
Message-ID: <20030717111750.18970b0a.matt@supplyedge.com> (raw)
In-Reply-To: <62793.212.219.213.253.1058429285.squirrel@jharris.homeip.net>

Yeah, the problem is the with reverse lookups.  It's a long, twisted scary story, but it should be resolved today.

Thanks for the reply's all!

-Matt

On Thu, 17 Jul 2003 09:08:05 +0100 (BST)
"Jamie Harris" <jamie@jharris.homeip.net> wrote:

> > It's not ident or port 113.
> 
> And you're 100% sure on this yeah?  You want to ensure that your server is
> reporting the port closed not silently dropping the packet (or the
> firewall silently dropping the packet) as you'll get exactly the behaviour
> you are describing - a very long wait while connections are retried to
> ident on the assumption that earlier packets were lost.
> 
> > Any and all suggestions would be greatly appreciated.  If you want some
> > more info, lemme know.
> 
> How are your reverse name lookups behaving?  Can you reverse lookup the
> hosts on both subnets.
> 
> cheers
> 
> Jamie...
> 
> -- 
> **  This message was transmitted on 100% recycled electrons **
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
================
Matt Hemingway
PCNAlert
www.pcnalert.com
626-585-2788
================


      reply	other threads:[~2003-07-17 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17  0:55 Port 25 Delay Matt Hemingway
2003-07-17  1:07 ` Jon Fullmer
2003-07-17  8:08 ` Jamie Harris
2003-07-17 18:17   ` Matt Hemingway [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=20030717111750.18970b0a.matt@supplyedge.com \
    --to=matt@supplyedge.com \
    --cc=jamie@jharris.homeip.net \
    --cc=linux-admin@vger.kernel.org \
    --cc=matt.hemingway@pcnalert.com \
    /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.