You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Plus, there's the whole issue of Accounting-Request and Acct-Delay-Time being updated on retransmits. Which contributes to congestive collapse when doing UDP to TCP proxying.
For TCP to UDP, it may be rarer, but it's possible. Should the proxy then take care of retransmitting packets over UDP?
I need to suggest some text.
The text was updated successfully, but these errors were encountered:
A forwarding server may either perform its forwarding function in a
pass through manner, where it sends retransmissions on as soon as it
gets them, or it may take responsibility for retransmissions, for
example in cases where the network link between forwarding and remote
server has very different characteristics than the link between NAS
and forwarding server.
Alex Clouter also mentioned we have the same issue on TCP -> TCP proxying, if the two connections have different throughputs
6613 etc. discuss UDP to TCP, but not TCP to UDP.
Plus, there's the whole issue of Accounting-Request and Acct-Delay-Time being updated on retransmits. Which contributes to congestive collapse when doing UDP to TCP proxying.
For TCP to UDP, it may be rarer, but it's possible. Should the proxy then take care of retransmitting packets over UDP?
I need to suggest some text.
The text was updated successfully, but these errors were encountered: