From: Matt Singerman <msingerman@ncemch.org>
To: pablo@blueoakdb.com
Cc: netfilter@lists.netfilter.org
Subject: Re: Problems configuring iptables
Date: Wed, 23 Aug 2006 15:07:16 -0400 [thread overview]
Message-ID: <44ECA764.8020205@ncemch.org> (raw)
In-Reply-To: <002e01c6c6e6$731fa7f0$9e0110ac@chaussy>
Pablo Sanchez wrote:
>
>
>
>> -----Original Message-----
>> From: netfilter-bounces@lists.netfilter.org
>> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of
>> Matt Singerman
>> Sent: Wednesday, August 23, 2006 2:58 PM
>> To: Martijn Lievaart
>> Cc: netfilter@lists.netfilter.org
>> Subject: Re: Problems configuring iptables
>>
>> 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?
>>
>
> Usually this means ssh isn't resolving properly. I'd guess your
> /etc/resolv.conf file isn't setup properly. Ensure the nameserver values
> point to your ISP.
>
> Cheers,
> ---
> Pablo Sanchez - Blueoak Database Engineering, Inc
> Ph: 819.459.1926 Toll free: 888.459.1926
> Cell: 819.918.9731 Pgr: pablo_p@blueoakdb.com
> Fax: 603.720.7723 (US)
>
>
>
Hi Pablo,
resolv.conf appears to be set up correctly. Also, if I turn off the
firewall and just let traffic flow through the bridge unfettered,
connections are much snappier. Actually, if I flush the rules, it is
just as fast with the firewall off. Any ideas what else it could be?
next prev parent reply other threads:[~2006-08-23 19:07 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 [this message]
2006-08-23 19:18 ` Martijn Lievaart
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=44ECA764.8020205@ncemch.org \
--to=msingerman@ncemch.org \
--cc=netfilter@lists.netfilter.org \
--cc=pablo@blueoakdb.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.