From: | BJ Freeman <bjfree(at)free-man(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: another can't connect |
Date: | 2009-06-29 21:50:14 |
Message-ID: | 6401561.31901246312217529.JavaMail.root@free-man.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for you help
found that this not connect problem is server wide.
not just Isolated to postgresql.
so tracking down what i did to mess it up
:D
BJ Freeman sent the following on 6/28/2009 8:23 PM:
> sorry about the post did not do a reply all and sent a personal replay
> yes in the chain I have
> ACCEPT all -- anywhere anywhere state
> RELATED,ESTABLISHED
> it is the next to last rule.
>
>
> Andrej sent the following on 6/28/2009 8:14 PM:
>> 2009/6/29 BJ Freeman <bjfree(at)free-man(dot)net>:
>>>>> ACCEPT tcp -- localhost localhost tcp
>>>>> dpt:postgres state NEW
>>>> What about established connections?
>>> tcp 0 0 127.0.0.1:5432 0.0.0.0:*
>>> LISTEN
>>> is the only line for that port
>> I think Chris meant "What about iptables rules for established connection?" ...
>>
>>
>> Cheers,
>> Andrej
>>
>>
>
--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.
From | Date | Subject | |
---|---|---|---|
Next Message | felix | 2009-06-29 22:08:51 | Database schema dumper |
Previous Message | Merlin Moncure | 2009-06-29 21:23:00 | Re: |