[Wireshark-users] help me people i am really a beguinner

2007-02-02 Thread dede dede
hi. I dont understand internet, I am a really beguinner user . I will study more but right now I need you help because I don´t understant completaly the user´s guide. my first doubt: I´ve captured a messenger package. there´s a lot of information about this package, but I wanna know what

[Wireshark-users] Wireshark 0.99.5 is now available

2007-02-02 Thread Gerald Combs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wireshark 0.99.5 has been released. What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development, and education. What's New Bug Fixes The following vulnerab

Re: [Wireshark-users] tcp packets too big !?

2007-02-02 Thread Ed . Staszko
It appears to be a mis-calculation of the length. If you subtract the sequence numbers in the first trace (2874589889 - 2874588441) you get 1448, the same value as in the second. I don't know the reason for the miscalculation, but the actual packet length does not exceed the MTU. Ed Staszko Te

Re: [Wireshark-users] tcp packets too big !?

2007-02-02 Thread Andreas Fink
could it be that your linux is supporting and using jumbo frames? In this case the MTU is much bigger On 02.02.2007, at 14:26, Christophe Lohr wrote: Hi, Wireshark shows (outgoing) tcp packet with a surprising size, larger than mss... Let's consider following "Client" and "Server": * S

Re: [Wireshark-users] CORBA message filtering

2007-02-02 Thread Leonard, Thomas J
Yes it is a CORBA based protocol. We have constructed messages and sent them via a notification channel. I can see the traffic, but had hoped to recover the message as well... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Guy Harris Sent: Friday, Feb

[Wireshark-users] tcp packets too big !?

2007-02-02 Thread Christophe Lohr
Hi, Wireshark shows (outgoing) tcp packet with a surprising size, larger than mss... Let's consider following "Client" and "Server": * Server [192.168.100.17] * # tshark -n "host 192.168.100.11 && host 192.168.100.17 && port 7575" > server.dump # netcat -l -p 7575 > /dev/null * Client [192.168.