Adam Jackson wrote:
On Wed, 2007-05-23 at 13:19 -0400, Steve Dickson wrote:
Will Woods wrote:
On Wed, 2007-05-23 at 09:45 -0400, Steve Dickson wrote:
I just installed test4 and notice Wireshark was not
available (not even as an option) but tcpdump was installed
by default... that is totally wrong..
Wireshark's still available, it's just not in the comps file for the
default spin. 'yum install wireshark' will still work post-install. Or
you could put it in your kickstart file if you're installing over the
network.
True... but when your asking asking someone to send you
an binary network trace (a *usable* network track at is) and
all they have (by default) is tcpdump, time is wasted
(on both sides) because they send up sending a useless
trace.. Plus having them yum install something they are
not familiar with can be a hard sell... why complicate
things by requiring people to take an extra step...
You know tcpdump can save pcap files, right?
Oh yeah... I've had a long and sorted history with
tcpdump.. The main problem is if you don't specify the
correct arguments, the binary trace it produces is useless
because it does not capture enough of the packet...
and lets not even start to talk about what protocols
it does *not* support... :-)
steved.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
