Accidentally replied instead of replied-to-all ...
--- On Fri, 12/19/08, Bruce Hyatt <brucejhyatt@yahoo.com> wrote:
> --- On Tue, 12/16/08, Ognjen Blagojevic
> <ognjen@etf.bg.ac.yu> wrote:
>
> > The simplest way to test if your network/iptables is
> set
> > correctly is to try to telnet the Postgres server:
> >
> > telnet server.example.com 5432
> >
> > If you get "Connect failed", you have a
> > network/iptables problem, if you get a blank screen,
> then
> > the network and iptables are both ok, and you should
> check
> > Postgres config files.
>
> I got 'connect failed' but here's my iptables
> chains:
>
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> RH-Firewall-1-INPUT all -- anywhere anywhere
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
> RH-Firewall-1-INPUT all -- anywhere anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain RH-Firewall-1-INPUT (2 references)
> target prot opt source destination
> ACCEPT all -- anywhere anywhere
> ACCEPT icmp -- anywhere anywhere
> icmp any
> ACCEPT ipv6-crypt-- anywhere anywhere
> ACCEPT ipv6-auth-- anywhere anywhere
> ACCEPT udp -- anywhere 224.0.0.251
> udp dpt:5353
> ACCEPT udp -- anywhere anywhere
> udp dpt:ipp
> ACCEPT all -- anywhere anywhere
> state RELATED,ESTABLISHED
> ACCEPT tcp -- anywhere anywhere
> state NEW tcp dpt:http
> REJECT all -- anywhere anywhere
> reject-with icmp-host-prohibited
>
> It doesn't look to me like anything is restricted
> (except icmp).
>
> Per postgresql.conf: listening '*' addresses on
> port 5432.
>
> pg_hba.conf IPv4:
> host all all 192.168.1.0 255.255.255.0
> trust
>
> The only possible anomaly I could find is that the
> configure-services gui reports postgresql status as '-p
> is stopped' but I can connect on the localhost.
>
> TIA,
> Bruce
