[svlug] ping results have changed. (why?)

[Bill Schoolcraft]

Hello,
	I've been messing with _ipfwadm_ rules here at home on my Linux
network for about 2 weeks (seems like two years) and finally got one
of my machines to go straight through my masq box to the
_hills.ccsf.cc.ca.us_ site (where my night courses are at) via telnet.

	That was a one time only success, can't get it to work again but
that's another assignment.

	My question now is, after having done that I cannot get a standard
ping exercise to work again? I have the results of a simple four count
ping on my local lan spew out close to 200 attempts with all but the 4
showing (DUP!) at the end.

	Ping seemed like such a "nothing to know" command but obviously there
is alot I don't know about it. Below is the truncated results saved to
file.

	Any "ping in a nutshell" comments would help.
-- 


    "If your life was nothing but sunshine, you'd just be a desert."
    _________________ (Future LINUX GURU Anthem) ___________________

                           Bill Schoolcraft
                    http://home.att.net/~wiliweld
-------------- next part --------------
# RESULTS FROM: ping -c4 192.168.7.4 (a machine on my local LAN)

PING 192.168.7.4 (192.168.7.4): 56 data bytes
64 bytes from 192.168.7.4: icmp_seq=0 ttl=64 time=1.2 ms
64 bytes from 192.168.7.4: icmp_seq=0 ttl=63 time=1.8 ms (DUP!)

# DELETED 180+ LINES HERE

64 bytes from 192.168.7.4: icmp_seq=2 ttl=2 time=33.9 ms (DUP!)
64 bytes from 192.168.7.4: icmp_seq=2 ttl=1 time=34.5 ms (DUP!)
64 bytes from 192.168.7.4: icmp_seq=3 ttl=64 time=1.0 ms

--- 192.168.7.4 ping statistics ---
4 packets transmitted, 4 packets received, +189 duplicates, 0% packet loss
round-trip min/avg/max = 1.0/17.7/34.5 ms