From: Matt Singerman <msingerman@ncemch.org>
To: "Gáspár Lajos" <swifty@freemail.hu>
Cc: netfilter@lists.netfilter.org
Subject: Re: Problems configuring iptables
Date: Thu, 24 Aug 2006 11:08:58 -0400 [thread overview]
Message-ID: <44EDC10A.40002@ncemch.org> (raw)
In-Reply-To: <44ED862A.7020603@freemail.hu>
Gáspár Lajos wrote:
> Martijn Lievaart írta:
>> 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
>>
>>
>>
> I am not sure... but maybe your script blocks the DNS service...
> Try it on your firewalled server and on a client behind the firewall...
> (host www.netfilter.org AND nslookup www.netfilter.org)
So I think the problem was that traffic was not able to flow back out
over the connection from within the firewall. I set up a ne rule
allowing all packets from the internal NIC to head out over the external
NIC, regardless of type or state, and that cleared up the problem
instantly. Thanks again for all the help, everyone!
prev parent reply other threads:[~2006-08-24 15:08 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
2006-08-24 10:57 ` Gáspár Lajos
2006-08-24 15:08 ` Matt Singerman [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=44EDC10A.40002@ncemch.org \
--to=msingerman@ncemch.org \
--cc=netfilter@lists.netfilter.org \
--cc=swifty@freemail.hu \
/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