Hello,
I've tried this again with version 1.0:
wireshark -k -i <(ssh [EMAIL PROTECTED] tshark -w - not tcp port 22)
and it works fine for me.
Could you perhaps try it again with version 1.0.0 and see if it also works for
you now?
Thanks, Joost
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On 08/01/08 at 11:03 +0100, Frederic Peters wrote:
> Lucas Nussbaum wrote:
>
> > I also tried tshark -i <(ssh rxa tshark -w - not tcp port 22). This
> > doesn't display anything.
> >
> > I've reported this bug upstream, at
> > http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2082 , but maybe yo
Lucas Nussbaum wrote:
> I also tried tshark -i <(ssh rxa tshark -w - not tcp port 22). This
> doesn't display anything.
>
> I've reported this bug upstream, at
> http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2082 , but maybe you
> could suggest something, since upstream is not responsive?
U
Package: wireshark
Version: 0.99.7-1
Severity: important
Hi,
I'm trying to use wireshark to analyze traffic captured remotely.
I tried to do wireshark -k -i <(ssh rxa tshark -w - not tcp port 22)
as described on http://wiki.wireshark.org/CaptureSetup/Pipes
But then the wireshark window just fre
4 matches
Mail list logo
