From: Martijn Lievaart <m@rtij.nl>
To: Matt Singerman <msingerman@ncemch.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Problems configuring iptables
Date: Wed, 23 Aug 2006 21:18:22 +0200 [thread overview]
Message-ID: <44ECA9FE.30605@rtij.nl> (raw)
In-Reply-To: <44ECA54A.2000905@ncemch.org>
Matt Singerman wrote:
> This did work, yes! Thanks! I am experiencing a new problem, though:
> it took an extremely long time for the connection to go through. Once
> it connected, it runs at normal speed, but it took a good 30 or 40
> seconds for ssh to prompt me for my password. What could be causing
> this? I am guessing it is some sort of routing issue?
>
Ah no. It's either reverse DNS or ident that trips you up. Ethereal is
your friend, look what goes on "at the wire".
M4
next prev parent reply other threads:[~2006-08-23 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 15:49 Problems configuring iptables Matt Singerman
2006-08-23 16:23 ` Ross A. Del Duca
2006-08-23 17:51 ` Matt Singerman
2006-08-23 17:54 ` Matt Singerman
2006-08-23 18:22 ` Martijn Lievaart
2006-08-23 18:58 ` Matt Singerman
2006-08-23 19:00 ` Pablo Sanchez
2006-08-23 19:07 ` Matt Singerman
2006-08-23 19:18 ` Martijn Lievaart [this message]
2006-08-24 10:57 ` Gáspár Lajos
2006-08-24 15:08 ` Matt Singerman
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=44ECA9FE.30605@rtij.nl \
--to=m@rtij.nl \
--cc=msingerman@ncemch.org \
--cc=netfilter@lists.netfilter.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