ICMP Source Quench has long been considered obsolete and harmful.
So it is very rare that stacks ever emit this kind of packet.
Even if they were emitted, all current stacks ignore this particular packet.
For TCP, a client that want to slow down the rate that a peer sends it data can just start shrinking the adverticed window instead.
regards
ronnie sahlberg
On Mon, Jun 1, 2009 at 12:00 PM, Merton Campbell Crockett
<m.c.crockett@xxxxxxxxxxxxxx> wrote:
Using various Wireshark's various tcp.analysis expressions I've
discovered that it is not uncommon for the Live Communications Server
2005 to transmit data to a Windows XP client faster than the latter
can transfer data to the application. It's unclear whether its simply
that Office Communicator 2005 can't keep up or if it is the result of
other activity on the client system.
Does the Windows XP TCP/IP protocol stack transmit ICMP Source Quench
packets when it is in danger of exhausting its buffer space?
I didn't find any ICMP Source Quench packets in the traffic that I had
captured. If it doesn't, everything is fine. :\ If it does, I may
need to search for a network device that is overly zealous in
filtering ICMP packets. :-(
Merton Campbell Crockett
m.c.crockett@xxxxxxxxxxxxxx
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
