Though I'm not in the core dev team, I think the main task of wireshark
is sniffing the net.
The main task of netdude is to edit packets in order to do tests with
packet injection later on.
Because, when sniffing, we want to be as passively as possible I think
it is not necessary
to do packet editing in Wireshark.
I've tested netdude too, and it is dead! The program still uses gtk+
(version 1) and isn't thus
compiling onder modern linux versions. And all the mailinglists for
netdude are dead, too.
So there is indeed the problem that there exists no graphical toolkit
for packetediting -
which is free - in the moment afaik. But, again, I think Wireshark is
not the right place for
packet editing.
Regards,
Marc.
Am 07.02.2011 19:20, schrieb Gregory Seidman:
I recently ran across Netdude<http://netdude.sf.net/>. I haven't played
with it, but it appears to have aims similar to Wireshark. It looks like
Wireshark is MUCH more mature, but there may be something to be learned
from it.
In particular, it's primary feature seems to be that it can edit fields in
packets. Has there been any thought toward Wireshark supporting editing? Is
there a strong reason not to (other than the technical difficulty involved,
which is not insignificant)?
--Greg
___________________________________________________________________________
Sent via: Wireshark-dev mailing list<wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
