From: "John Jones" <jjones@merlintechnologies.com>
To: netfilter@lists.samba.org
Subject: RE: tcpdump behavior not getting all packets in promisc mode
Date: Mon, 3 Jun 2002 18:22:54 -0700 [thread overview]
Message-ID: <005201c20b66$5a516a50$6301a8c0@JJONES1> (raw)
In-Reply-To: <20020604011417.39761.qmail@web10408.mail.yahoo.com>
> The plug and play reports an intel pro 100, but that
> is likely just the chip that reports the board
> manufacturer is long forgotten by me. I thought it
> rather interesting that Linux never asked for any sort
> of driver for this card during set up? I bought
> another lan card last night (SMC) and plugged it in
> ,but do not have it configured yet
That card uses the EEPRO100 driver, and many Linux installs have that
pre-built into the kernel that the distro is sent out with.
> > 2. Do you have another machine you can plug into the
> > hub to:
> Yes but only one machine is now running linux, does
> microsoft provide a tcpdump type utility? I think I'll
> dump the suse linux and load redhat first?
Go to: www.ethereal.com and download that (freeware). I use it, and
it is essentially what you are looking for in a GUI'ed tcpdump.
John
next prev parent reply other threads:[~2002-06-04 1:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <007a01c20ac1$3071b780$4000a8c0@thought>
2002-06-03 13:36 ` tcpdump behavior not getting all packets in promisc mode Art Reisman
2002-06-03 22:13 ` Nick Drage
2002-06-04 0:43 ` Art Reisman
2002-06-04 0:50 ` Antony Stone
2002-06-04 1:14 ` Art Reisman
2002-06-04 1:22 ` John Jones [this message]
2002-06-04 1:25 ` John Jones
2002-06-04 1:43 ` Antony Stone
2002-06-02 23:52 Art Reisman
2002-06-03 4:33 ` Alexey Talikov
2002-06-03 4:39 ` Ramin Alidousti
2002-06-03 4:47 ` Alexey Talikov
2002-06-03 4:55 ` Ramin Alidousti
2002-06-03 9:40 ` Nick Drage
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005201c20b66$5a516a50$6301a8c0@JJONES1' \
--to=jjones@merlintechnologies.com \
--cc=netfilter@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox