Subject: Re: More info on telnet problems
To: Alex Barclay <alex@vsys.com>
From: Jeremy D. Worrells - 4097358 <jworrell@nunic.nu.edu>
List: port-sun3
Date: 06/05/1997 11:10:26
Alex Barclay wrote:
>
> Could you also produce a "netstat -rn" to get the routing table.
>
Sure. Here it is:
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Interface
default 205.142.124.255 UGS 0 18 - le0
9 205.142.124.254 UG 0 0 - le0
89 205.142.124.254 UG 0 0 - le0
127.0.0.1 127.0.0.1 UH 1 6 - lo0
129.213 205.142.124.254 UG 0 0 - le0
137.39 205.142.124.254 UG 0 0 - le0
139.87 205.142.124.254 UG 0 0 - le0
140.204 205.142.124.254 UG 0 0 - le0
143.159 205.142.124.254 UG 0 0 - le0
146.198 205.142.124.254 UG 0 0 - le0
146.199 205.142.124.254 UG 0 0 - le0
151.104 205.142.124.254 UG 0 0 - le0
152.67 205.142.124.254 UG 0 0 - le0
155.201 205.142.124.254 UG 0 0 - le0
158.101 205.142.124.254 UG 0 0 - le0
161.71 205.142.124.254 UG 0 0 - le0
192.41.247 205.142.124.254 UG 0 0 - le0
192.73.58 205.142.124.254 UG 0 0 - le0
192.92.21 205.142.124.254 UG 0 0 - le0
192.92.68 205.142.124.254 UG 0 0 - le0
192.92.77 205.142.124.254 UG 0 0 - le0
192.103.141 205.142.124.254 UG 0 0 - le0
192.128.3 205.142.124.254 UG 0 0 - le0
192.147.72 205.142.124.254 UG 0 0 - le0
192.168.1 205.142.124.254 UG 0 0 - le0
192.168.3 205.142.124.254 UG 0 0 - le0
192.168.4 205.142.124.254 UG 0 0 - le0
192.168.10 205.142.124.254 UG 0 0 - le0
192.168.30 205.142.124.254 UG 0 0 - le0
192.168.31 205.142.124.254 UG 0 0 - le0
194.39.127 205.142.124.254 UG 0 0 - le0
198.115.120 205.142.124.254 UG 0 0 - le0
198.115.121 205.142.124.254 UG 0 0 - le0
198.115.122 205.142.124.254 UG 0 0 - le0
198.115.126 205.142.124.254 UG 0 0 - le0
198.175.212 205.142.124.254 UG 0 0 - le0
200.51.106 205.142.124.254 UG 0 0 - le0
204.79.199.2 205.142.124.254 UGH 0 0 - le0
204.164.160 205.142.124.254 UG 0 0 - le0
204.164.161 205.142.124.254 UG 0 0 - le0
204.164.162 205.142.124.254 UG 0 0 - le0
204.164.165 205.142.124.254 UG 0 0 - le0
204.212.145 205.142.124.254 UG 0 0 - le0
205.142.124 link#1 UC 0 0 - le0
205.142.124.22 0:a0:24:24:30:9c UHL 0 0 - le0
205.142.124.90 127.0.0.1 UGHS 3 49581 - lo0
205.142.124.98 0:c0:4f:b3:9f:1e UHL 0 0 - le0
205.142.124.254 8:0:2:f:9d:55 UHL 48 0 - le0
205.142.124.255 link#1 UHL 2 1840 - le0
205.142.125 205.142.124.254 UG 1 299532 - le0
205.158.1 205.142.124.254 UG 0 0 - le0
205.180.73 205.142.124.254 UG 0 0 - le0
206.136.9 205.142.124.254 UG 0 203 - le0
206.137.68 205.142.124.254 UG 0 0 - le0
208.145.162.68 205.142.124.254 UGH 0 0 - le0
208.204.174 205.142.124.254 UG 0 0 - le0
> The DUP replies can occur if you ping on the broadcast address. You
> don't appear to be doing this but if your default route is to the
> broadcast address then you might see this behaviour.
>
Sure, I understand. I'm gonna try the default route set to .254.
>
> So is your default route to 205.142.124.255 or 205.142.124.0 instead
> of a more usual policy of having the gateway 1 in from the ends at 1
> or 254.
>
> I don't guarantee that this is the fault but here is my output:
>
> A ping to 166.93.219.64 (Our broadcast address)
> alta > ping 166.93.219.64
> PING 166.93.219.64 (166.93.219.64): 56 data bytes
> 64 bytes from 166.93.219.79: icmp_seq=0 ttl=255 time=10.550 ms
> 64 bytes from 166.93.219.80: icmp_seq=0 ttl=255 time=41.028 ms (DUP!)
> 64 bytes from 166.93.219.66: icmp_seq=0 ttl=255 time=49.735 ms (DUP!)
> 64 bytes from 166.93.219.74: icmp_seq=0 ttl=64 time=50.134 ms (DUP!)
> 64 bytes from 166.93.219.71: icmp_seq=0 ttl=255 time=50.523 ms (DUP!)
> 64 bytes from 166.93.219.87: icmp_seq=0 ttl=64 time=50.876 ms (DUP!)
> 64 bytes from 166.93.219.82: icmp_seq=0 ttl=254 time=51.220 ms (DUP!)
>
> Alex.
>
Thanks again.
--
Jeremy Worrells Undergraduate - Computer Science
jworrell@nunic.nu.edu National University
jworrell@priacc.com http://nunic.nu.edu/~jworrell