[Wireshark-users] TCP Segment of a reassembled PDU from a NetApp filer

Hi I've read previous posts regarding TCP Segment of a reassembled PDU, but I still can't figure out why it is happening in my environment. I'm using NDMP between a Windows 2003 system and a NetApp filer. I'm able to have a problem-free NDMP conversation between this same Windows 2003 system

Re: [Wireshark-users] TCP Segment of a reassembled PDU from aNetApp filer

There's two questions here: 1) why does TCP Segment of a reassembled PDU happen at all? 2) why, in some cases, don't you eventually see the reassembled PDU? The answer to 1) is because some protocols running atop TCP either put more than one of their PDUs in a TCP segment, with

Re: [Wireshark-users] wireshark questions

Ive just installed wireshark on my windows XP machine,and Im trying to capture a packet thats on a Linux box.But,at the same time,I have a copy of packet in a pdf document on my XP machine.Here's my questions: 1)Is there a way to capture the packet from my XP machine to the linux box? - If you

[Wireshark-users] List of ciphers supported by Wireshark

Where can I find the list of ciphers supported by Wireshark? I checked http://wiki.wireshark.org/SSL, but didn't see this list there. Thanks! tl ___ Wireshark-users mailing list Wireshark-users@wireshark.org

Re: [Wireshark-users] How to decode non-standard SSL traffic

Hi Tomas Thanks for suggestions! I did enable SSL debug, and learned a lot from it. I saw that Wireshark did not like my RSA-format key file, but liked the self-signed SSL key file just fine. And the log file does show that SSL records are identified and processed. But, I still can't see the

Re: [Wireshark-users] How to decode non-standard SSL traffic

Thanks for the reply. I have no idea why it isn't decoding. I've attached the whole ssl debug file. Any clues? What else can I do to help debug this? Thanks tl ssl_init keys string 192.168.11.114,4433,data,/tmp/server.key ssl_init found host entry 192.168.11.114,4433,data,/tmp/server.key

Re: [Wireshark-users] Decode SSL?

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, January 22, 2007 11:42 AM To: [EMAIL PROTECTED] Cc: wireshark-users@wireshark.org Subject: Re: [Wireshark-users] Decode SSL? Thanks for the reply, Mike. I have been able to

Re: [Wireshark-users] Decode SSL?

Hi Steve That was the problem! Openssl s_server uses TCP port 4433 by default. Once I did the right-click and Decode as SSL, decoding occurred. I was even able to decode a file created with tcpdump that contained SSL traffic. Thanks very much for the help! tl What port is the exchange going

Re: [Wireshark-users] Using the SSL rsasnakeoil example

Argh, that's it. Thanks very much! tl You're missing the field that specifies the protocol contained within the ssl stream (http). The fields are ip,port,protocol,key. Try this: 127.0.0.1,443,http,Z:\Tools\Wiresharkrsasnakeoil2.key Steve ___