https://github.com/keithw/mosh/issues/464
for details.
On Sun, Feb 9, 2014 at 2:14 PM, Outback Dingo wrote:
> Wow, cool... be my guest.
>
>
> On Sun, Feb 9, 2014 at 5:13 PM, Dave Taht wrote:
>>
>> What is so hard about fixing dropbear?
>>
>> On S
IMHO, most of the dscp related recomendations were not taken up by the universe.
in particular, the AFxx classifications are, in the words of one
author of the relevant rfc, nuts.
openssh so far as I know uses IPTOS_THROUGHPUT and IPTOS_LOWDELAY
as you do, so goferthat. (so does multiple shapers
On Sat, Nov 23, 2013 at 1:52 AM, Catalin Patulea wrote:
> I noticed that dropbear sets IPTOS_LOWDELAY on all sockets:
> https://secure.ucc.asn.au/hg/dropbear/file/14342451d3df/dbutil.c#l190
>
> This is great for interactive sessions, but not ideal for bulk
> transfer sessions like scp or sftp. Man
OK, well...
On Mon, Oct 21, 2013 at 8:02 PM, Anders Kaseorg wrote:
> On Mon, 21 Oct 2013, Dave Taht wrote:
>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]:
>> ioctl(TIOCSCTTY): Input/output error
>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]: /dev/pts/
he setsockopt change
would be asserted on the flow, thus reprioritizing packets
possibly in flight?
>
> Cheers,
> Matt
>
> On Wed, Sep 28, 2011 at 04:58:24AM -0700, Dave Taht wrote:
>> Setting the TCLASS (TOS) field requires different setsockopt
>> params on ipv6 than ip
It would be mildly better to set the bulk bit for scp transfers where possible.
On Wed, Sep 28, 2011 at 4:58 AM, Dave Taht wrote:
> Setting the TCLASS (TOS) field requires different setsockopt
> params on ipv6 than ipv4.
>
> as per:
>
> http://www.bufferbloat.net/projects/
Setting the TCLASS (TOS) field requires different setsockopt
params on ipv6 than ipv4.
as per:
http://www.bufferbloat.net/projects/cerowrt/issues/249
---
dbutil.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/dbutil.c b/dbutil.c
index b3a119f..2739d2f 100644
--- a
