This is Interesting: Free IT Magazines  
Home > Archive > Snort > September 2004 > [Snort-users] delayed acks and sliding protocol question (semi-snort related)





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [Snort-users] delayed acks and sliding protocol question (semi-snort related)
dissolved

2004-09-24, 5:46 pm

This is a multi-part message in MIME format.

------=_NextPart_000_0004_01C4A1D7.97B923B0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

I know this is not directly related to snort, but I am trying to decipher
some stuff I am seeing while just using the snort -v switch. I've also been
curious about these 2 questions for a while. Figured this was the best place
to ask.



1. Can anyone elaborate on the relation (if any) between the sliding
window protocol and the delayed acknowledgement algorithm. I am under the
impression that when the sliding protocol is used, the delayed ack algorithm
is not. Is that a correct assumption? Does it have something to do with
the delayed ack timer never going off when the sliding protocol is being
used?



Also:

2. Say a client and server are communicating large chunks of data, and
sliding protocol is being used obviously. The client advertises a window
size of say 3000 bytes. The server sends 3 segments (each 1000 bytes each)
to the client. The client then ACKs.



Now I know you DO NOT have to send the full amount of the advertised window
size. I heard you can send less, and it will be ok. Let's say the server
only sends 2000 bytes of data to the client who advertised a window size of
3000 bytes. Wont the client still be expecting the 1000 bytes?? Will the
delayed ack timer go off or possible retransmission from the server occur
since the ack wont come back?



Any insight would be greatly appreciated it.

Thanks

Ryan


------=_NextPart_000_0004_01C4A1D7.97B923B0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>I know this is not directly =
related to
snort, but I am trying to decipher some stuff I am seeing while just =
using the
snort –v switch.&nbsp; I’ve also been curious about these 2
questions for a while. Figured this was the best place to =
ask.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>1. </span></font><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Can anyone elaborate =
on&nbsp; the
relation&nbsp; (if any) between&nbsp; the sliding window protocol and =
the
delayed acknowledgement algorithm.&nbsp; I am under the impression that =
when
the sliding protocol is used, the delayed ack algorithm is not.&nbsp; Is =
that a
correct assumption?&nbsp; Does it have something to do with the delayed =
ack
timer never going off when the sliding protocol is being =
used?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Also:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;2. &nbsp;</span></font><font =
size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>Say a =
client and
server are communicating large chunks of data, and sliding protocol is =
being
used obviously.&nbsp; The client advertises a window size of say 3000
bytes.&nbsp; The server sends 3 segments (each 1000 bytes each) to the
client.&nbsp; The client then ACKs.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Now I know you DO NOT have to send the full amount of =
the
advertised window size. I heard you can send less, and it will be =
ok.&nbsp;
Let’s say the server only sends 2000 bytes of data to the client =
who
advertised a window size of 3000 bytes.&nbsp; Wont the client still be
expecting the 1000 bytes??&nbsp; Will the delayed ack timer go off or =
possible
retransmission from the server occur since the ack wont come =
back?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Any insight would be greatly appreciated =
it.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Ryan<o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0004_01C4A1D7.97B923B0--



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
________________________________________
_______
Snort-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists...nfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf....ist=snort-users
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2010 webservertalk.com