Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL - Mailing list pgsql-general

From John R Pierce
Subject Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Date
Msg-id 4EFA2086.2080104@hogranch.com
Whole thread Raw
In response to Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (Jacques Lamothe <JLamothe@allconnect.com>)
Responses Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
List pgsql-general
On 12/27/11 11:34 AM, Jacques Lamothe wrote:
> Output
>
> [root@vpdb1 ~]# iptables -L -vn
> Chain INPUT (policy ACCEPT 44094 packets, 6327K bytes)
>   pkts bytes target     prot opt in     out     source               destination
>      0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:5436
>
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>   pkts bytes target     prot opt in     out     source               destination
>
> Chain OUTPUT (policy ACCEPT 43575 packets, 6143K bytes)
>   pkts bytes target     prot opt in     out     source               destination
> [root@vpdb1 ~]#

it appears there's no iptables based firewall configured at all, the
default policy is ACCEPT, so there's really no point in that rule for 5436


--
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast


pgsql-general by date:

Previous
From: Jacques Lamothe
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Next
From: Adrian Klaver
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL