> $ ping cvsup.postgresql.org
> PING rs.postgresql.org: 64 byte packets
> 64 bytes from 64.39.15.238: icmp_seq=0. time=57. ms
> 64 bytes from 64.39.15.238: icmp_seq=1. time=70. ms
> Perhaps there is a routing problem somewhere between you and 64.39.15.238?
> That machine is not physically at hub (looks like it's a Rackspace site)
> so there might be connectivity issues that are different from hub's.
> What do you get from tracerouting to cvsup.postgresql.org?
*slaps forehead*
I didn't catch on to the different network, and 64.x has always been a
problem on my firewall/masquerading box since I'm also on a 64.x subnet
and it keeps wanting to put in default routes for a class A network. So
it is all a problem on my end.
I had done some testing at another location yesterday, when I was
finding that cvsup connections were being rejected.
Any hints on how to supress this default route when the network is
configured?
Sorry Marc for the false alarm (today anyway ;)
- Thomas
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
