All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Leangen" <netfilter@leangen.net>
To: netfilter@lists.netfilter.org
Subject: Tracking down the source of proxy problem
Date: Mon, 1 May 2006 18:13:43 +0900	[thread overview]
Message-ID: <NEBBKBPLMLNABNADCIPACEOMBPAB.netfilter@leangen.net> (raw)


Hello!

I have a network with an iptables-based firewall/proxy. Behind the proxy is
a machine running Postgres. Recently, many changes were made to the
installation.

Connecting to the Postgres DB works from within the network, but not from
without. I've run out of ideas for tracking down the error...

Could anybody kindly pass on some wise advice?


firewall iptables (in port number edited):

  *nat
  :PREROUTING ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  :OUTPUT ACCEPT [0:0]
  -A PREROUTING -p tcp --dport ##INPORT## -j DNAT --to 192.168.2.10:5432
  -A PREROUTING -p udp --dport ##INPORT## -j DNAT --to 192.168.2.10:5432
  -A POSTROUTING -o ppp0 -j MASQUERADE
  COMMIT


db machine iptables:

  *filter
  :INPUT DROP [1:242]
  :FORWARD DROP [0:0]
  :OUTPUT ACCEPT [0:0]
  :LOG_DROP - [0:0]
  :LOG_ACCEPT - [0:0]
  :icmp_packets - [0:0]
  -A INPUT -p tcp -s 192.168.0.0/16 -m tcp --dport 5432 -j ACCEPT
  -A INPUT -j DROP


Thank you!!



             reply	other threads:[~2006-05-01  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01  9:13 David Leangen [this message]
2006-05-01 10:41 ` Tracking down the source of proxy problem Rob Sterenborg
2006-05-01 11:33   ` David Leangen
2006-05-01 12:21     ` Rob Sterenborg
2006-05-01 12:52       ` David Leangen

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=NEBBKBPLMLNABNADCIPACEOMBPAB.netfilter@leangen.net \
    --to=netfilter@leangen.net \
    --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.