This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Mike, it's interesting, the "mtr" command doesn't have any problem seeing rtstats.unidata.ucar.edu, although traceroute fails. The traceroute problem to your domain seems to occur on all wunderground.com machines, not just n8 (idd). Anyway, here's the netstat: root@n8:~# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 66.28.250.128 0.0.0.0 255.255.255.224 U 0 0 0 eth0 66.28.250.160 0.0.0.0 255.255.255.224 U 0 0 0 eth0 10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 66.28.250.161 0.0.0.0 UG 0 0 0 eth0 Jeff On Thu, 19 May 2005, Mike Schmidt wrote: > Jeff, > > I forgot to ask you for the output of "netstat -rn from n8" > > mike > > On May 19, 6:43pm, Jeff Masters wrote: > > Subject: Re: 20050512: Routing from winderground to idd and rtstats > > > > Hi Mike, the machine also has the name idd.wunderground.com, which is > > connected to an IP number. Would making that name in your allow fix > > things? The machine knows itself as n8.wunderground.com, which as you > > said, is an internal IP only. > > > > Jeff >