Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ssh client_loop send disconnnect from Dom0 -> DomU (NetBSD 10.0_BETA/Xen)



Hi,

On 22.06.23 08:36, RVP wrote:
Can you see any errors from sshd(8) in the logs on the DomU?
If not, run the sshd server standalone like this:

```
/usr/sbin/sshd -Dddd -E/tmp/s.log
```

then post the `s.log' file after you run something like:

```
$ ssh -E/tmp/c.log -vvv XXX.NET 'dd if=/dev/zero bs=1m count=10000 msgfmt=quiet' >/dev/null
```

on the Dom0.


Thanks for all the good points and suggestions. I have picked up the last one and temporarely ran sshd on the DomU in debug mode, while repeating the exact same test with ssh and dump.

Here are the logs:

- Dom0: https://paste.petermann-it.de/?0c56870be0c9e8b1#9bCJT4C2hTBMUWzgDu84o6ipccjC7kNQzdofQtCaLUyz

- DomU: https://paste.petermann-it.de/?8185479d13b60bbd#98azwgVmfsz5aQ8dPswwCD2yn2mTnM9kstVLvNv8JUKy

During this test, the error count on the affected interfaces did not increase further:

```
netbsd_netif_rx_bytes{interface="re0"} 64759716902
netbsd_netif_tx_bytes{interface="re0"} 1017162986389
netbsd_netif_errors{interface="re0"} 0
netbsd_netif_rx_bytes{interface="lo0"} 99500058
netbsd_netif_tx_bytes{interface="lo0"} 99500058
netbsd_netif_errors{interface="lo0"} 0
netbsd_netif_rx_bytes{interface="bridge0"} 1047528461564
netbsd_netif_tx_bytes{interface="bridge0"} 1049530231106
netbsd_netif_errors{interface="bridge0"} 0
netbsd_netif_rx_bytes{interface="xvif1i0"} 33842998
netbsd_netif_tx_bytes{interface="xvif1i0"} 31012168535
netbsd_netif_errors{interface="xvif1i0"} 26
```

The relevant part from the client log...

```
debug2: channel 0: window 1900544 sent adjust 196608

debug2: tcpwinsz: 197420 for connection: 3

debug2: channel 0: window 1966080 sent adjust 131072

debug2: tcpwinsz: 197420 for connection: 3

debug2: channel 0: window 1966080 sent adjust 131072

debug2: tcpwinsz: 197420 for connection: 3

debug2: channel 0: window 1966080 sent adjust 131072

debug3: send packet: type 1

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 e[write]/0 fd 6/7/8 sock -1 cc -1 io 0x01/0x00)



Connection to srv-net closed by remote host.

Transferred: sent 1086580, received 7869273016 bytes, in 393.9 seconds

Bytes per second: sent 2758.8, received 19980159.5

debug1: Exit status -1
```

...and from the server log...

```
debug2: channel 0: rcvd adjust 131072

debug2: channel 0: rcvd adjust 131072

debug2: channel 0: rcvd adjust 196608

debug2: channel 0: rcvd adjust 131072

debug2: channel 0: rcvd adjust 131072

debug2: channel 0: rcvd adjust 131072

process_output: ssh_packet_write_poll: Connection from user user 192.168.2.50 port 60196: Host is down

debug1: do_cleanup

debug3: PAM: sshpam_thread_cleanup entering

debug3: mm_request_receive: entering

debug1: do_cleanup

debug1: PAM: cleanup

debug1: PAM: closing session

debug1: PAM: deleting credentials

debug3: PAM: sshpam_thread_cleanup entering
```

...appears a bit like both parties blaming each other... client tells the remote host has closed the connection, and the remote host complains about the client beeing down.


Kind regards
Matthias

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Home | Main Index | Thread Index | Old Index