On Wed, 17 Apr 2002, Mikael Olsson wrote: :> for transport my current thinking is: :> :> for the ssh transport connection, we use nagle by default only if it is :> a session channel with a pty and shell or exec channel (and agent :> forward?) : :Hm, wait. I'm not following you here. If you have a pty, you're :being interactive, so ... why enable nagle in that particular :case, even by default?
because you want nagle by default for interactive-only sessions. nagle was invented to reduce the number of small segments on the network for cases such as this. the complication is due to nagle being per TCP, and in SSH we have multiple channels per TCP. so the idea is if we have a channel where nagle can cause problems (eg., X11) we disable nagle for the transport TCP. and if you don't like the default heuristics, there will be a nodelay yes/no dial. :(This is the opposite of what you've been doing :up to 3.0.x, is it not?) yes, and that behaviour was inherited from ssh 1.2.X. _______________________________________________ Firewalls mailing list [EMAIL PROTECTED] http://lists.gnac.net/mailman/listinfo/firewalls
