Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
| От | John R Pierce |
|---|---|
| Тема | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL |
| Дата | |
| Msg-id | 4EFA2086.2080104@hogranch.com обсуждение исходный текст |
| Ответ на | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL (Jacques Lamothe <JLamothe@allconnect.com>) |
| Ответы |
Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
|
| Список | 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 по дате отправления: