Wireshark-users: [Wireshark-users] text2pcap_windowsXP
From: "Faten SOLTANI" <[email protected]>
Date: Mon, 23 Mar 2009 16:54:30 +0100 (CET)
Hi
I'm using C++2005, and Windows XP.
if it's possible to explan to me step by step  how to use and excute
text2pcap progrem.
Regards




 Send Wireshark-users mailing list submissions to
> 	[email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://wireshark.org/mailman/listinfo/wireshark-users
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
>
> You can reach the person managing the list at
> 	[email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wireshark-users digest..."
>
>
> Today's Topics:
>
>    1. Re: TCP: window scaling (Sake Blok)
>    2. Re: TCP: window scaling (Jo Verstraelen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 23 Mar 2009 13:17:51 +0100
> From: "Sake Blok" <[email protected]>
> Subject: Re: [Wireshark-users] TCP: window scaling
> To: "Community support list for Wireshark"
> 	<[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Jo,
>
> Both ends of the tcp connection need to support Window scaling for it to
> be used:
>
> "This option is an offer, not a promise; both sides must send Window Scale
> options in their SYN segments to enable window scaling in either
> direction."
> (From http://tools.ietf.org/html/rfc1323)
>
> In your trace, host 63.245.209.93 does not support Window scaling, as the
> SYN/ACK that it sends does not have the window scaling option. Therfore no
> window scaling will be used and Wireshark displays non-scaled values.
>
> Hope this helps,
> Cheers,
>      Sake
>   ----- Original Message -----
>   From: Jo Verstraelen
>   To: Community support list for Wireshark
>   Sent: Monday, March 23, 2009 11:58 AM
>   Subject: Re: [Wireshark-users] TCP: window scaling
>
>
>   Hi Sake,
>
>
>
>   Here you go: http://denuitlaat.be/tcp/windowscaled1.pcap .
>   It shows that a session is started with a SYN and the option ws is
> present (ws = 2). The segments following do not show a scaled window
> size.
>
>
>
>   Regards,
>
>   jo
>
>
>
>
> ------------------------------------------------------------------------------
>
>   From: [email protected]
> [mailto:[email protected]] On Behalf Of Sake Blok
>   Sent: maandag 23 maart 2009 11:40
>   To: Community support list for Wireshark
>   Subject: Re: [Wireshark-users] TCP: window scaling
>
>
>
>   Hi Jo,
>
>
>
>   The window size should consistently be displayed within one TCP session.
> Between sessions, there could be difference, because either there is no
> scaling, or the SYN, SYN/ACK were not present in the tracefile. If that
> does not explain the differences you see, could you provide a small
> capture showing this issue?
>
>
>
>   Cheers,
>
>   Sake
>
>
>
>     ----- Original Message -----
>
>     From: Jo Verstraelen
>
>     To: [email protected]
>
>     Sent: Monday, March 23, 2009 11:03 AM
>
>     Subject: [Wireshark-users] TCP: window scaling
>
>
>
>     Hi,
>
>
>
>     Is there a reason why sometimes in a connection which received a
> window scaler (syn;syn,ack) , the window size is
>
>     shown as "number (scaled)" and sometimes just as "number" (non scaled)
> in the next segments. Cause in the last case its not
>
>     possible to know the exact window size as the window scale factor is
> non present in the segments after the syn; syn,ack.
>
>     Kind regards,
>
>     Jo
>
>
>
>
>
>
> ----------------------------------------------------------------------------
>
>     ___________________________________________________________________________
>     Sent via:    Wireshark-users mailing list
> <[email protected]>
>     Archives:    http://www.wireshark.org/lists/wireshark-users
>     Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>                  mailto:[email protected]?subject=unsubscribe
>
>
>
> ------------------------------------------------------------------------------
>
>
>   ___________________________________________________________________________
>   Sent via:    Wireshark-users mailing list
> <[email protected]>
>   Archives:    http://www.wireshark.org/lists/wireshark-users
>   Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>                mailto:[email protected]?subject=unsubscribe
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://www.wireshark.org/lists/wireshark-users/attachments/20090323/4d7e7f30/attachment.htm
>
> ------------------------------
>
> Message: 2
> Date: Mon, 23 Mar 2009 13:59:36 +0100
> From: "Jo Verstraelen" <[email protected]>
> Subject: Re: [Wireshark-users] TCP: window scaling
> To: "Community support list for Wireshark"
> 	<[email protected]>
> Message-ID:
> 	<[email protected]al>
> Content-Type: text/plain; charset="us-ascii"
>
> Sake,
>
>
>
> That explains...
> But that doesn't change the fact that it is bizar, because the
> destination ip of the server in the pcap file is a webserver of the
> Mozilla corp. So a 100MBit+ webserver that does not support window
> scaling?
>
>
>
> Thanks for the info,
>
> jo
>
>
>
> ________________________________
>
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Sake Blok
> Sent: maandag 23 maart 2009 13:18
> To: Community support list for Wireshark
> Subject: Re: [Wireshark-users] TCP: window scaling
>
>
>
> Jo,
>
>
>
> Both ends of the tcp connection need to support Window scaling for it to
> be used:
>
>
>
> "This option is an offer, not a promise; both sides must send Window
> Scale options in their SYN segments to enable window scaling in either
> direction."
>
> (From http://tools.ietf.org/html/rfc1323)
>
>
>
> In your trace, host 63.245.209.93 does not support Window scaling, as
> the SYN/ACK that it sends does not have the window scaling option.
> Therfore no window scaling will be used and Wireshark displays
> non-scaled values.
>
>
>
> Hope this helps,
>
> Cheers,
>
>      Sake
>
> 	----- Original Message -----
>
> 	From: Jo Verstraelen <mailto:[email protected]>
>
> 	To: Community support list for Wireshark
> <mailto:[email protected]>
>
> 	Sent: Monday, March 23, 2009 11:58 AM
>
> 	Subject: Re: [Wireshark-users] TCP: window scaling
>
>
>
> 	Hi Sake,
>
>
>
> 	Here you go: http://denuitlaat.be/tcp/windowscaled1.pcap .
> 	It shows that a session is started with a SYN and the option ws
> is present (ws = 2). The segments following do not show a scaled window
> size.
>
>
>
> 	Regards,
>
> 	jo
>
>
>
>
> ________________________________
>
>
> 	From: [email protected]
> [mailto:[email protected]] On Behalf Of Sake Blok
> 	Sent: maandag 23 maart 2009 11:40
> 	To: Community support list for Wireshark
> 	Subject: Re: [Wireshark-users] TCP: window scaling
>
>
>
> 	Hi Jo,
>
>
>
> 	The window size should consistently be displayed within one TCP
> session. Between sessions, there could be difference, because either
> there is no scaling, or the SYN, SYN/ACK were not present in the
> tracefile. If that does not explain the differences you see, could you
> provide a small capture showing this issue?
>
>
>
> 	Cheers,
>
> 	Sake
>
>
>
> 		----- Original Message -----
>
> 		From: Jo Verstraelen <mailto:[email protected]>
>
> 		To: [email protected]
>
> 		Sent: Monday, March 23, 2009 11:03 AM
>
> 		Subject: [Wireshark-users] TCP: window scaling
>
>
>
> 		Hi,
>
>
>
> 		Is there a reason why sometimes in a connection which
> received a window scaler (syn;syn,ack) , the window size is
>
> 		shown as "number (scaled)" and sometimes just as
> "number" (non scaled) in the next segments. Cause in the last case its
> not
>
> 		possible to know the exact window size as the window
> scale factor is non present in the segments after the syn; syn,ack.
>
> 		Kind regards,
>
> 		Jo
>
>
>
>
>
>
> ________________________________
>
>
>
> ________________________________________________________________________
> ___
> 		Sent via:    Wireshark-users mailing list
> <[email protected]>
> 		Archives:
> http://www.wireshark.org/lists/wireshark-users
> 		Unsubscribe:
> https://wireshark.org/mailman/options/wireshark-users
>
> mailto:[email protected]?subject=unsubscribe
>
>
> ________________________________
>
>
>
> ________________________________________________________________________
> ___
> 	Sent via:    Wireshark-users mailing list
> <[email protected]>
> 	Archives:    http://www.wireshark.org/lists/wireshark-users
> 	Unsubscribe:
> https://wireshark.org/mailman/options/wireshark-users
>
> mailto:[email protected]?subject=unsubscribe
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://www.wireshark.org/lists/wireshark-users/attachments/20090323/4ad48d22/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> Wireshark-users mailing list
> [email protected]
> https://wireshark.org/mailman/listinfo/wireshark-users
>
>
> End of Wireshark-users Digest, Vol 34, Issue 46
> ***********************************************
>