Samuel Thibault wrote: > > In the default (NAT) configuration of a VirtualBox VM, in all VMs > > so far I could "ssh 10.0.2.2" to log into the VM host. With these > > new Hurd VMs, this is not the case > > Uh? What symptom do you actually get?
The ssh command hangs. Here's a 'ssh -v -v -v' output for 10.0.2.2: ======================================================= OpenSSH_9.2p1 Debian-2, OpenSSL 3.0.8 7 Feb 2023 debug1: Reading configuration data /home/bruno/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolve_canonicalize: hostname 10.0.2.2 is address debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/bruno/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/bruno/.ssh/known_hosts2' debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling debug3: ssh_connect_direct: entering debug1: Connecting to 10.0.2.2 [10.0.2.2] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 ======================================================= And here's the same thing for a different destination: ======================================================= OpenSSH_9.2p1 Debian-2, OpenSSL 3.0.8 7 Feb 2023 debug1: Reading configuration data /home/bruno/.ssh/config debug1: /home/bruno/.ssh/config line 2: Applying options for panoramix debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/bruno/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/bruno/.ssh/known_hosts2' debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling debug2: resolving "panoramix" port 22 debug3: resolve_host: lookup panoramix:22 debug3: ssh_connect_direct: entering debug1: Connecting to 192.168.178.30 [192.168.178.30] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/bruno/.ssh/id_rsa type -1 debug1: identity file /home/bruno/.ssh/id_rsa-cert type -1 debug1: identity file /home/bruno/.ssh/id_ecdsa type -1 debug1: identity file /home/bruno/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/bruno/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/bruno/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/bruno/.ssh/id_ed25519 type -1 debug1: identity file /home/bruno/.ssh/id_ed25519-cert type -1 debug1: identity file /home/bruno/.ssh/id_ed25519_sk type -1 debug1: identity file /home/bruno/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/bruno/.ssh/id_xmss type -1 debug1: identity file /home/bruno/.ssh/id_xmss-cert type -1 debug1: identity file /home/bruno/.ssh/id_dsa type -1 debug1: identity file /home/bruno/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.1 debug1: compat_banner: match: OpenSSH_6.1 pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK ... ======================================================= When I try the debugging advice [1]: # settrans -fga /dev/netdde /hurd/netdde $ ssh 10.0.2.2 prints some messages from the irq_handler [9] and then locks up the machine solid. $ ping 8.8.8.8 likewise Debugging with gdb shows 2 threads: the main thread doing connect(), and a second thread waiting for a timeout. As expected. > What does tcpdump say about it? How would I use it? I've never used tcpdump before. Bruno [1] https://www.debian.org/ports/hurd/hurd-install
