From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Port is open but I am unable to connect
Date: Wed, 08 Sep 2004 07:35:04 -0400 [thread overview]
Message-ID: <1094643303.1903.3.camel@wolfpack.ljm.dom> (raw)
In-Reply-To: <413EA8E9.3090700@list.idg.dk>
On Wed, 2004-09-08 at 02:38, Jacob Friis Larsen wrote:
> > i would content that while you believe your source IP is 1.2.3.4 in this
> > scenario--it; in fact, is not.
>
> I know.
> 1.2.3.4 is just for the example :)
>
> > try:
> >
> > iptables -A INPUT -j LOG --log-prefix "FW DROP INPUT: "
> >
> > and see what the logs have to say about it.
>
> This will log all incoming packets?
setting the above as you last rule, in combination with setting the
POLICY of the INPUT chain to DROP, will log all packets dropped by the
INPUT chain. similarly:
iptables -A OUTPUT -j LOG --log-prefix "FW DROP OUTPUT: "
will log all packets dropped by the OUTPUT chain; which in your case,
should show you what Aleksandar already pointed out--you don't allow
ESTABLISHED packets out through the OUTPUT chain.
-j
--
Jason Opperisano <opie@817west.com>
next prev parent reply other threads:[~2004-09-08 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 19:27 Port is open but I am unable to connect Jacob Friis Larsen
2004-09-07 19:35 ` Sascha Reissner
2004-09-08 6:34 ` Jacob Friis Larsen
2004-09-07 20:19 ` Jason Opperisano
2004-09-08 6:38 ` Jacob Friis Larsen
2004-09-08 11:35 ` Jason Opperisano [this message]
2004-09-07 20:59 ` Aleksandar Milivojevic
2004-09-08 6:47 ` Jacob Friis Larsen
2004-09-09 10:17 ` Jacob Friis Larsen
2004-09-09 12:20 ` Jason Opperisano
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=1094643303.1903.3.camel@wolfpack.ljm.dom \
--to=opie@817west.com \
--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 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.