Message-ID: <4F996B98.3040508@consistentstate.com>
Date: Thu, 26 Apr 2012 09:36:56 -0600
From: Kevin Kempter <cs_dba@consistentstate.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-admin@postgresql.org
Subject: Re: psql: could not connect to server: No route to host
References: <4F98D19D.6060303@consistentstate.com>
	<23291.1335415839@sss.pgh.pa.us>
In-Reply-To: <23291.1335415839@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 04/25/2012 10:50 PM, Tom Lane wrote:
> Kevin Kempter<cs_dba@consistentstate.com>  writes:
>> I can scp files between the servers
> Really?
>
>> $ psql -h 192.168.1.125
>> psql: could not connect to server: No route to host
> Because that is not a Postgres problem, that is a network connectivity
> problem.  I'd bet that there's something wrong with the VM
> configuration, such that the VM host isn't connecting 192.168.1.* in one
> VM to 192.168.1.* in the other.
>
> 			regards, tom lane

Scientific Linux turns on the firewall by default. It lets me scp via 
username & passwd but wouldn't allow the port 5432 tcp connection till I 
disabled it.  I like Scientific because it seems that they are a large 
team and as a project seem to have better long term viability than other 
RH based projects but a couple of their defaults drive me nuts. Like 
this one, and the default install of yum-autoupdate