Mailing List Archive: [Bug 556] TCP_NODELAY not set completely for port forwarding

[Bug 556] TCP_NODELAY not set completely for port forwarding

Aug 26, 2003, 8:56 AM

Post #1 of 3 (652 views)

http://bugzilla.mindrot.org/show_bug.cgi?id=556

------- Additional Comments From markus@openbsd.org 2003-08-27 02:56 -------
sshd already sets nodelay for the connection, but conditionally, and
only for interactive sessions, so this is the well known problem:

why does sshd traditionally set no delay only for interactive sessions.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 556] TCP_NODELAY not set completely for port forwarding [ In reply to ]

bugzilla-daemon at mindrot

Aug 26, 2003, 8:57 AM

Post #2 of 3 (638 views)

Permalink

http://bugzilla.mindrot.org/show_bug.cgi?id=556

------- Additional Comments From markus@openbsd.org 2003-08-27 02:57 -------
i don't see how your patch affects port forwarding......

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 556] TCP_NODELAY not set completely for port forwarding [ In reply to ]

bugzilla-daemon at mindrot

Aug 26, 2003, 9:12 AM

Post #3 of 3 (632 views)

Permalink

http://bugzilla.mindrot.org/show_bug.cgi?id=556

------- Additional Comments From briang@oasisadvancedengineering.com 2003-08-27 03:12 -------
This patch does not specifically fix port forwarding, as it fixes the problem
where TCP_NODELAY is not set on all types of connections. I was using SSH for
port forwarding, with a non-interactive connection, and was receiving problems
since TCP_NODELAY was not being set.

By adding this patch, or something similar, the buffering problem I saw with
small but frequent data packets.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.