Steven> I can't get a connection, dns propagation must be lagging. Steven> Could someone tell me the new IP address for xemacs.org? Yep. It is 199.184.165.136. Steven> Thanks, Steven> STH -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

Steven> $ host cvs.xemacs.org Steven> cvs.xemacs.org. has address 130.225.247.90 This is correct; cvs.xemacs.org is a completely different host from the other xemacs.org hosts. Why you're not getting through on the traceroute, I don't know. I'm not having any problems. (And unfortunately I can't easily test connectivity directly because one of the types of packet our packet-filcher filches is ICMP.) -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py

You might try `fft' which uses TCP instead of ICMP. This email is to inform you of release '2.0-Beta3' of 'FFT' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/fft/ The changes in this release are as follows: This revision adds a new trace engine under the hood that can detect stateful firewalls, reduce no-reply hops, et al. It is, however, an early access beta of the new engine. Project description: FFT is an alternative traceroute program for displaying the route packets take to an IP network host. Unlike Van Jacobson's traceroute, which is available on almost every platform today, FFT uses TCP in order to elicit ICMP TIME_EXCEEDEDs or other IP route data. As a result, FFT often executes much faster and sees behind some configurations of firewalls. It also does AS number and netblock name lookups en route. Most importantly, FFT can trace specific TCP-based protocol routes (not just IP) to assist network engineers in isolating network and application problems. $ fft xemacs.org Tracing __________________________!_+ Hop FFT trace to xemacs.org (199.184.165.136): 1 (64.162.142.121) = 16 ms 2 dist1-vlan60.snfc21.pbi.net (216.102.187.130) = 20 ms 3 bb1-g8-0.snfc21.pbi.net (209.232.130.82) = 16 ms 4 bb2-p14-0.snfc21.pbi.net (64.161.124.54) = 15 ms 5 206.223.120.73 = 29 ms 6 ge4-0.core4.sfrn.ca.rcn.net (208.59.255.19) = 18 ms 7 pos1-2.core3.lnh.md.rcn.net (208.59.95.210) = 121 ms 8 ge4-0.core2.lnh.md.rcn.net (207.172.15.18) = 94 ms 9 pos5-0-0.core3.mrf.va.rcn.net (207.96.92.130) = 95 ms 10 fe12-1-0.sys-core1b.mrf.va.rcn.net (208.59.255.86) = 96 ms 11 xemacs.org (199.184.165.136) [endpoint] = 87 ms --- Vladimir ------------------------------------------------------------------------ Vladimir G. Ivanovic http://leonora.org/~vladimir 2770 Cowper St. vladimir(a)acm.org Palo Alto, CA 94306-2447 +1 650 678 8014 "SJT" == Stephen J Turnbull <stephen(a)xemacs.org&gt; writes: SJT> Why you're not getting through on the traceroute, I don't know. I'm SJT> not having any problems. (And unfortunately I can't easily test SJT> connectivity directly because one of the types of packet our SJT> packet-filcher filches is ICMP.)