Hello,
The ssh TcpRcvBuf option [1] works well when running an ssh client to
indicate that the ssh client should have a large TCP receive buffer.
This is a good workaround until bug 206716 [2] is fixed for people who
want their ssh client to receive a lot of data.
I have an ssh server that
Hello,
Please identify any false statements (particularly statement 7 which
accuses FreeBSD 10.1 of having a bug):
1. openssh limits the size of "the outgoing buffer" to 65KB
2. (1) limits bandwidth on high BDP links.
3. FreeBSD 10.1 supplied openssh/HPN tries to fix (2) by increasing the
John-Mark,
I'm going to rearrange the conversation a bit in the quotes below:
On 8/26/15 3:32 PM, John-Mark Gurney wrote:
So, I looked at what getsockopt SO_RCVBUF returns, and it returns:
case SO_RCVBUF:
optval = so-so_rcv.sb_hiwat;
Which is NOT
On 8/26/15 5:46 PM, David DeSimone wrote:
On 8/26/15 1:24 AM, John-Mark Gurney wrote:
94146 ssh 6.686140 CALL read(0x4,0x7fff6c70,0x4000)
94146 ssh 6.686154 GIO fd 4 read 4096 bytes
[ read of stdin (/dev/zero) snipped)
It would be interesting to know how long from
On 8/25/15 3:47 PM, Chris Stankevitz wrote:
Can anyone explain my abysmally small TCP window?
So I believe this is the story:
1. openssh limits the size of some outgoing buffer to 65KB
2. openssh/HPN tries to improve on this by increasing the size of the
outgoing buffer to match getsockopt
On 8/27/15 6:14 AM, Kurt Lidl wrote:
# tcp options for long-haul speedups
kern.ipc.maxsockbuf=4194304 # (2 * default 2097152)
net.inet.tcp.mssdflt=1448 # (default 576)
net.inet.tcp.sendbuf_max=4194304# (2 * default 2097152)
net.inet.tcp.recvbuf_max=4194304
John-Mark,
Thanks again. I appreciate you teaching me how to fish. I basically
spent all morning reading kdump output.
On 8/26/15 1:24 AM, John-Mark Gurney wrote:
It really looks like we should set TCPRcvBufPoll by default on
FreeBSD...
According to /etc/ssh/sshd_config, TCPRcvBufPoll
John-Mark,
Thank you for your reply.
On 8/25/15 6:03 PM, John-Mark Gurney wrote:
Chris Stankevitz wrote this message on Tue, Aug 25, 2015 at 15:47 -0700:
# cat /dev/urandom | ssh root@host 'cat /dev/null'
Don't use this for testing... use /dev/zero or some other device
that can produce
On 8/25/15 4:11 PM, Bjoern A. Zeeb wrote:
On 25 Aug 2015, at 22:47 , Chris Stankevitz ch...@stankevitz.com wrote:
Can anyone recommend some tools/tricks to figure out what in FreeBSD and/or
base SSH is limiting the send/recv buffer and/or TCP window?
if you have the memory, try
Hi,
# cat /dev/urandom | ssh root@host 'cat /dev/null'
I use the above ssh command over a high-BDP WAN link (80 ms @ 100 Mbps).
tcpdump shows I am TCP window limited to 64 KBytes (yielding 5 Mbps).
iperf with default options gets the window opened to 500 KBytes
(yielding 35 Mbps).
Both
10 matches
Mail list logo
