| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Cc: | thomas(at)pgsql(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: cvsup trouble |
| Date: | 2001-09-21 15:49:03 |
| Message-ID: | 3BAB616F.AD8523D@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> $ 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gowey, Geoffrey | 2001-09-21 16:32:16 | an already existing alter table drop column ?!?!?! |
| Previous Message | Tom Lane | 2001-09-21 14:41:34 | Re: cvsup trouble |