Newsgroups: comp.archives
Path: utzoo!utgpu!news-server.csri.toronto.edu!math.lsa.umich.edu!math.lsa.umich.edu!emv
From: dpz@action.rutgers.edu (David Paul Zimmerman)
Subject: [tcp-ip] Re: need enhanced ping
Message-ID: <1990Aug24.190100.19651@math.lsa.umich.edu>
Followup-To: comp.protocols.tcp-ip
Sender: emv@math.lsa.umich.edu (Edward Vielmetti)
Reply-To: dpz@action.rutgers.edu (David Paul Zimmerman)
Organization: University of Michigan, Department of Mathematics
Date: Fri, 24 Aug 90 19:01:00 GMT
Approved: emv@math.lsa.umich.edu (Edward Vielmetti)
X-Original-Newsgroups: comp.protocols.tcp-ip
Lines: 23

Archive-name: dimacs-ping/24-Aug-90
Original-posting-by: dpz@action.rutgers.edu (David Paul Zimmerman)
Original-subject: Re: need enhanced ping
Archive-site: dimacs.rutgers.edu [128.6.75.16]
Archive-directory: /pub
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)

I can help you with 1) and 2).  A couple of years ago I made modifications to
the Berkeley ping to allow writing and reading of route-record packets.  That
is dimacs.rutgers.edu:~ftp/pub/ping.shar.  I also found that 4.3BSD hosts
didn't do the right thing per the RFCs with ICMP echo request packets that had
record-route set (and by association, timestamp request packets also).
dimacs.rutgers.edu:~ftp/pub/rr.shar are kernel changes to 4.3BSD to deal with
that.  Although I've submitted both back to Berkeley, I don't know if they've
made 4.3-Tahoe, -Reno, or 4.4.  I've also gotten a report of a portability bug
for rr.shar, but haven't dealt with it yet (change the caddr_t definition of
"opts" to u_char *).

			David (from the Norse meaning "hacker of wire")
-- 
David Paul Zimmerman                                     dpz@dimacs.rutgers.edu
Systems Programmer						    rutgers!dpz
Rutgers Univ Center for Discrete Math and Theoretical Computer Science (DIMACS)
