Please answer these questions before submitting your issue. Thanks!

1. What version of Go are you using (go version)?

   > go version
   go version go1.6 linux/amd64

2. What operating system and processor architecture are you using (go env)?

   Ubuntu 14.04.4 LTS

   > go env
   GOARCH="amd64"
   GOBIN=""
   GOEXE=""
   GOHOSTARCH="amd64"
   GOHOSTOS="linux"
   GOOS="linux"
   GOPATH="/home/wolf/goworkspace"
   GORACE=""
   GOROOT="/usr/local/go"
   GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
   GO15VENDOREXPERIMENT="1"
   CC="gcc"
   GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
   CXX="g++"
   CGO_ENABLED="1"

3. What did you do?
   (Use play.golang.org to provide a runnable example, if possible.)

   If I use Dial() on an SSH Client more than once, the second returned net.Conn can not read/write until the first Dial completes. The write's appear to work fine on the returned net.Conn, but aren't actually delivered until the first one is Close()d.

   Example:

           sshClient, err := ssh.Dial("tcp", serverstr, sshConfig)
           remoteConn, err := sshClient.Dial("tcp", remoteString)
           defer remoteConn.Close()
           remoteConn2, err := sshClient.Dial("tcp", remoteString)

   In this code, remoteConn2 will not send bytes until remoteConn is Close()d, and remoteConn2 will not Read() until remoteConn is closed.

4. What did you expect to see?

   I expect every Dial()ed connection to be independent of the others and able to fully multiplex. I don't want to have to wait for previous Dial()ed connections to close.

   This greatly hinders throughput.

5. What did you see instead?

   I must Close() previously Dial()ed connections if I want any new ones to work.