home *** CD-ROM | disk | FTP | other *** search
- X-Gateway-Source-Info: INTERNET
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!wupost!usc!news.service.uci.edu!unogate!mvb.saic.com!tgv.com!info-multinet
- Date: 20 NOV 92 21:05:23 GMT
- Newsgroups: vmsnet.networks.tcp-ip.multinet
- X-Return-path: <info-multinet-relay@TGV.COM>
- X-RFC822-From: adelman (Kenneth Adelman) @ TGV.COM
- From: adelman@TGV.COM
- Subject: Re: Another TCPDUMP question...
- Organization: The INFO-MULTINET Community
- Message-ID: <36A00FB320NOV92210523@TGV.COM>
- Nntp-Posting-Host: Mvb.Saic.Com
- Lines: 40
-
- > Why, when I do a MU TCPDUMP ETHER HOST CECIL I get dumps like this:
-
- > 19:42:10.14 cecil cecil loopback 46:
- > 0000 0100 0100 4361 796d 616e 2053 7973 ......Cayman Sys
- > 7465 6d73 2047 6174 6f72 426f 7820 6c6f tems GatorBox lo
- > 6f70 6261 636b 2070 6163 6b65 742e opback packet.
- > 19:42:10.36 cecil AppleTalk-Multicast 0024 28:
- > 0001 809b 0604 0003 0000 8901 a1ac 0000 ................
- > 025d 0000 0000 0000 0000 025d .].........]
- > 19:42:11.07 arp who-has eos.cstp.umkc.edu tell cecil
-
- This means that cecil sent an ARP request for the host eos,
- probably because it wants to send a packet to it (perhaps eos is a
- default router and we're trying to send a query to the DNS or somesuch).
-
- > 19:42:11.08 arp reply eos.cstp.umkc.edu is-at aa:0:4:0:2c:4
-
- EOS replies to the request with its Ethernet address.
-
- The odd thing here is that we would next expect to see a packet
- from EOS to cecil, but don't.
-
- > 19:42:11.08 vax2.cstp.umkc.edu.nfs > eos.cstp.umkc.edu.9f1f062b:
- > reply ok OK 96
- > [...]
- > 19:42:11.41 vax2.cstp.umkc.edu.nfs > eos.cstp.umkc.edu.a11f062b:
- > reply ok OK 128
- > 19:42:11.45 vax2.cstp.umkc.edu.nfs > eos.cstp.umkc.edu.a01f062b:
- > reply ok ENOENT 28
- > 19:42:11.59 vax2.cstp.umkc.edu.nfs > eos.cstp.umkc.edu.a21f062b:
- > reply ok OK 128
- > 19:42:11.65 vax2.cstp.umkc.edu.nfs > eos.cstp.umkc.edu.a31f062b:
- > reply ok ENOENT 28
-
- Either VAX2 or EOS has the same ETHERNET address if we're
- seeing these packets. Try repeating the trace with the /ETHER
- switch so we can see the Ethernet address as well as the IP address.
-
- Ken
-