Subject: More info on telnet problems
To: None <port-sun3@NetBSD.ORG, netbsd-help@NetBSD.ORG>
From: Alex Barclay <>
List: port-sun3
Date: 06/05/1997 11:18:07
Jeremy D. Worrells writes:
 > Thanks all for your hints and tips. Here is some information that has been
 > requested by people:
 > For Jeremy, the output of ifconfig -a:
 > 	inet netmask 0xffffff00 broadcast
 > lo0: flags=8009<UP,LOOPBACK,MULTICAST>
 > 	inet netmask 0xff000000 
 > ppp0: flags=8010<POINTOPOINT,MULTICAST>
 > ppp1: flags=8010<POINTOPOINT,MULTICAST>
 > tun0: flags=10<POINTOPOINT>
 > tun1: flags=10<POINTOPOINT>
 > Also, the output from netstat -an -f inet:

Could you also produce a "netstat -rn" to get the routing table.

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.

So is your default route to or 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 (Our broadcast address)
alta > ping
PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=255 time=10.550 ms
64 bytes from icmp_seq=0 ttl=255 time=41.028 ms (DUP!)
64 bytes from icmp_seq=0 ttl=255 time=49.735 ms (DUP!)
64 bytes from icmp_seq=0 ttl=64 time=50.134 ms (DUP!)
64 bytes from icmp_seq=0 ttl=255 time=50.523 ms (DUP!)
64 bytes from icmp_seq=0 ttl=64 time=50.876 ms (DUP!)
64 bytes from icmp_seq=0 ttl=254 time=51.220 ms (DUP!)


Alex Barclay			E-mail:
Vsys, Inc.
731 N.Weber, Suite 202		Tel:    +1 719 635 8066 x 17
Colorado Springs, CO 80903	Fax:    +1 719 635 1420