Bruno Haible via Bug reports for the GNU Hurd, le mar. 14 janv. 2025 15:39:45 +0100, a ecrit: > 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 > =======================================================
So it didn't even manage to establish a tcp connection. > When I try the debugging advice [1]: > # settrans -fga /dev/netdde /hurd/netdde I don't think the network driver is at stake, but rather the tcp/ip stack. > > What does tcpdump say about it? > > How would I use it? I've never used tcpdump before. tcpdump -n -i /dev/eth0 -s 1500 and you'll get the exchanged packets details. Samuel
