Thank you. That was the problem. I don't know why I didn't think of that
before. In fact, that is what I thought was happening!! I just didn't
bother to check if tcpdump had an option to disable DNS lookups.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Arni Raghu
> Sent: October 14, 1999 5:32 PM
> To: Trenton D. Adams
> Cc: Linux-Net
> Subject: Re: tcpdump problem
>
>
> Hi,
> do this::
>
> tcpdump -n
>
> and see what happens..
>
> hth,
> Arni
>
> "Trenton D. Adams" wrote:
> >
> > I have a very odd problem. I would appreciate it if someone was able to
> > help me. If I do a tcpdump of packets on my local network here
> at home with
> > my laptop, it works fine. But on the other hand, if I do a tcpdump of
> > packets on the local network at school with my laptop, it doesn't always
> > work. Sometimes it works if I wait awhile for the packets, but
> not always.
> > For example. If I go "tcpdump -x -i eth0", it should do a dump of any
> > packets on the network, right? If I do a ping to any machine
> at school it
> > doesn't work all the time. It does work sometimes if I wait a
> really long
> > time. What is going on, anyone have any clues?
> >
> > p.s.
> > As far as I know, there is no way the IS guys can stop me from
> doing a dump
> > of packets to and from my machine!!! Am I mistaken?
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-net" in
> > the body of a message to [EMAIL PROTECTED]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
