On Sun, 25 Jun 2023, Matthias Petermann wrote:
Somewhere between 2) and 3) there should be the answer to the question.
``` 08:52:07.595831 ARP, Request who-has vhost2.lan tell srv-net.lan, length 28 08:52:07.595904 ARP, Reply vhost2.lan is-at 88:ae:dd:02:a4:03 (oui Unknown), length 28 08:52:07.595919 ARP, Reply vhost2.lan is-at 88:ae:dd:02:a4:03 (oui Unknown), length 28 08:52:07.595921 ARP, Reply vhost2.lan is-at 88:ae:dd:02:a4:03 (oui Unknown), length 28 08:52:07.595921 ARP, Reply vhost2.lan is-at 88:ae:dd:02:a4:03 (oui Unknown), length 28 08:52:07.595926 ARP, Reply vhost2.lan is-at 88:ae:dd:02:a4:03 (oui Unknown), length 28 [...] 08:52:07.627118 IP srv-net.lan.ssh > vhost2.lan.54243: Flags [R], seq 3177171235, win 0, length 0 ``` Well, this doesn't look like an ARP timeout issue. The DomU does the ARP-query and gets back an answer from the Dom0 right away. In fact the Dom0 sends multiple replies to the query (I don't know what that means nor if it's relevant to your issue...); then sshd on the DomU gets a EHOSTDOWN and exits, and the kernel sends a reset TCP packet in response to more data coming to that socket. I may have to replicate your setup to dig into this. Maybe this weekend. Send instructions on how to set-up Xen. In the meantime, can you: 1. post the output of `ifconfig' on all your DomUs 2. tell me if `dhcpcd' is running on the DomUs? -RVP
