From: Greg Cope <gregcope@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Help debugging iptables firewall....
Date: Tue, 25 Jan 2005 17:59:13 +0000 [thread overview]
Message-ID: <c0e9781f05012509594af6ebb9@mail.gmail.com> (raw)
In-Reply-To: <27594E8BA9D5CA458F5EF87D88B6B48F01991D@pxtvjoexd01.pxt.primeexalia.com>
I think we are getting there:
The one you suggested gives an error:
Starting firewall: ^[[Aiptables v1.2.9: multiple -o flags not allowed
Looking at tcpdump on a few machines it looks like the packets are
getting through - but nothing gets sent:
17:57:18.168655 ex.e-dba.net.32931 > trotter.e-dba.net.1521: S
965495617:965495617(0) win 5840 <mss 1460,sackOK,timestamp 2026024
0,nop,wscale 0> (DF) [tos 0x10]
And then nothing else - sadly I am not a tcpdump expert.....
Any clues? I am at a loss as to why this was working and now it does not.....
Greg
On Tue, 25 Jan 2005 09:46:20 -0800, Gary W. Smith <gary@primeexalia.com> wrote:
> Are you getting the connection coming back? Try
>
> $IPTABLES -A FORWARD -o $DMZ_IFACE -o $LAN_IFACE -j ACCEPT
>
> And see if it makes any difference. Forward works in both directions.
> We typically allow established,related to return the path that it came
> from. You might need to do the same.
>
>
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of Greg Cope
> Sent: Tuesday, January 25, 2005 9:25 AM
> To: netfilter@lists.netfilter.org
>
> Subject: Re: Help debugging iptables firewall....
>
> 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
>
>
next prev parent reply other threads:[~2005-01-25 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 17:46 Help debugging iptables firewall Gary W. Smith
2005-01-25 17:59 ` 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:13 Gary W. Smith
2005-01-25 17:24 ` 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=c0e9781f05012509594af6ebb9@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