From: Greg Cope <gregcope@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Help debugging iptables firewall....
Date: Tue, 25 Jan 2005 17:24:59 +0000 [thread overview]
Message-ID: <c0e9781f050125092466365224@mail.gmail.com> (raw)
In-Reply-To: <27594E8BA9D5CA458F5EF87D88B6B48F01991C@pxtvjoexd01.pxt.primeexalia.com>
Hi Gary,
Pinholes? If you mean specific IP to specific IP:PORT on specfic
interfaces then yes.
DB is an oracle listener (port 1521)
I have these:
# for ssh to db server from webserver
$IPTABLES -A FORWARD -p tcp --dport 22 -i $DMZ_IFACE -s $DMZ_EDGE_IP
-o $LAN_IFACE -d $TROT_IP -j ACCEPT
$IPTABLES -A FORWARD -p tcp --dport 1521 -i $DMZ_IFACE -s $DMZ_EDGE_IP
-o $LAN_IFACE -d $TROT_IP -j ACCEPT
I added 2 of your examples one before one after, and only see:
Jan 25 17:21:43 gateway kernel: Oracle 1521 [tcp] before: IN=eth1
OUT=eth2 SRC=192.168.254.3 DST=192.168.0.5 LEN=60 TOS=0x00 PREC=0x00
TTL=63 ID=30447 DF PROTO=TCP SPT=32907 DPT=1521 WINDOW=5840 RES=0x00
SYN URGP=0
Which would imply that the rule is ok and the packets goes through -
but why I am not getting a connection?
Thanks,
Greg
On Tue, 25 Jan 2005 09:13:04 -0800, Gary W. Smith <gary@primeexalia.com> wrote:
> I would recommend that you put a log entry for the protocol(s) or IP to
> IP connections that you want to debug across the DMZ. I did this while
> trying to debug some IPSEC traffic.
>
> -A FORWARD -p tcp -m tcp --dport 1433 -j LOG --log-prefix "MySQL [tcp]:
> " --log-level 1
> -A FORWARD -p udp -m udp --dport 1433 -j LOG --log-prefix "MySQL [udp]:
> " --log-level 1
>
> Put this at the beginning of the chain (tweak it for whatever DB you
> need) and then just watch the calls to make sure that you are see the
> flow that you want. When you are done move them down to the end of the
> chain, if they are still hitting then you are loosing packets.
>
> BTW, are you running pinholes (point to point IP for each port you want
> open)? What DB?
>
> Gary Wayne Smith
>
>
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of Greg Cope
> Sent: Tuesday, January 25, 2005 8:54 AM
> To: netfilter@lists.netfilter.org
> Subject: Help debugging iptables firewall....
>
> Hi All,
>
> I have a 3 interface firewall (internet, dmz, lan).
>
> For some reason a dmz host can longer ssh or connect to a DB server on
> the lan(it could before).
>
> Nothing seems to get logged with a $IPTABLES -A FORWARD -j LOG
> --log-prefix "FORWARD DENY: " rule. And when I disable the FW and
> enable the plain routing it seems to be able to connect ok.
>
> At a loss as to why this would not work without logging something.
>
> Firewall and Webserver are FC1, DB server is Redhat AS3.
>
> Could someone suggest some ideas on debuging this?
>
> Any ideas gratefully received.
>
> Greg
>
>
next prev parent reply other threads:[~2005-01-25 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 17:13 Help debugging iptables firewall Gary W. Smith
2005-01-25 17:24 ` Greg Cope [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 22:11 Gary W. Smith
2005-01-26 7:19 ` Greg Cope
2005-01-25 20:00 Gary W. Smith
2005-01-25 22:06 ` Greg Cope
2005-01-25 18:31 Gary W. Smith
2005-01-25 19:08 ` Greg Cope
2005-01-25 18:09 Gary W. Smith
2005-01-25 18:18 ` Greg Cope
2005-01-25 17:46 Gary W. Smith
2005-01-25 17:59 ` Greg Cope
2005-01-25 16:53 Greg Cope
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=c0e9781f050125092466365224@mail.gmail.com \
--to=gregcope@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox