Kevin Steves wrote:
>
> as i posted earlier, we now disable nagle for TCP and
> X11 forwarding endpoints.
Great! :)
> 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?
(This is the opposite of what you've been doing
up to 3.0.x, is it not?)
--
Mikael Olsson, Clavister AB
Storgatan 12, Box 393, SE-891 28 �RNSK�LDSVIK, Sweden
Phone: +46 (0)660 29 92 00 Mobile: +46 (0)70 26 222 05
Fax: +46 (0)660 122 50 WWW: http://www.clavister.com
"Senex semper diu dormit"
_______________________________________________
Firewalls mailing list
[EMAIL PROTECTED]
http://lists.gnac.net/mailman/listinfo/firewalls
