Hi, Is there a way to tell why I'm getting frequent "Connection reset by peer" all of a sudden? I'm using a FreeBSD machine, plugged via eithernet to a Linksys router running DD-WRT, to another Linksys 50 feet away running DD-WRT, both of them WDS'd together, plugged via ethernet to another FreeBSD machine. With debug cranked, I see : debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r0 i0/0 o0/0 fd 4/5) debug3: channel 0: close_fds r 4 w 5 e 6 Read from remote host 10.0.0.1: Connection reset by peer Connection to 10.0.0.1 closed. debug1: Transferred: stdin 0, stdout 0, stderr 90 bytes in 106.9 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.8 debug1: Exit status -1 Thanks, Tuc
Tuc at T-B-O-H wrote:> Is there a way to tell why I'm getting frequent > "Connection reset by peer" all of a sudden? > > I'm using a FreeBSD machine, plugged via eithernet to a Linksys > router running DD-WRT, to another Linksys 50 feet away running DD-WRT, > both of them WDS'd together, plugged via ethernet to another FreeBSD machine. > With debug cranked, I see :1) check the SSH server's logs to see if there's any logged message corresponding to the disconnects. If the problem is easy to reproduce, you could run sshd in debug mode in the foreground (eg "/path/to/sshd -ddde -p 2022" then connect to port 22). 2) if that doesn't have anything, or has the same "connection reset by peer message" then you probably will need to run tcpdump or similar to see which end is generating the TCP RST (in theory it should be only generated by one of the TCP endpoints but it could also be generated by, eg an intermediate NAT box). -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.