Changes between Initial Version and Version 1 of Ticket #10034, comment 8
- Timestamp:
- Jul 2, 2014 6:42:49 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #10034, comment 8
initial v1 1 It looks like NAT doesn't send window updates to the guest when it forwards data to the real destination. Since guest is directly connected to NAT engine, it can fill its receive buffers very fast. When the window closes and no window update comes from NAT, guest stops sending until its persi t timer fires and prompts it to do window probe. It gets back fully opened window and can send the next burst of data, after which the problem repeats itself.1 It looks like NAT doesn't send window updates to the guest when it forwards data to the real destination. Since guest is directly connected to NAT engine, it can fill its receive buffers very fast. When the window closes and no window update comes from NAT, guest stops sending until its persist timer fires and prompts it to do window probe. It gets back fully opened window and can send the next burst of data, after which the problem repeats itself.
