I know this isn't "selfhosting" as most people imagine it, but it is about hosting services on own hardware, hence why I'm posting in this community.
I'm supposed to help a teacher set up a networking exercise where pairs of computers are connected directly on a crossover cable and can access services (echo, HTTP, SSH, FTP) on each other. Every computer is identical: Windows 10 host, one VirtualBox VM running Linux Mint with a bridged adapter in promiscuous mode. Each host and VM has its own static link-local IP address.
The problem is, the VMs can't talk to each other, and I don't know why.
From one VM, I can ping itself, its host, and the remote host, but not the remote VM. Each host can ping itself, the local VM, the remote host, but not the remote VM. I've tried connecting both hosts to a layer-2 switch, with the same result.
Can someone point me at the one thing that I'm obviously doing wrong?
(edit) I've also tried to set the default gateway to the host's, remote host's, and remote VM's address, but nothing changed.
Running Linux on metal isn't an option. In the past, the classroom computers used to dual boot Windows and Ubuntu, but the Windows install got so bloated (the software too, not just Windows) that it needs the full SSD.
@rtxn I'm no expert in networking with VirtualBox, but did you already had a look into the manual?
https://www.virtualbox.org/manual/ch06.html#network_udp_tunnel
I'll give it a try tomorrow, thanks.
Although I'd still prefer to know why the VMs won't talk over simple Ethernet.
@rtxn Maybe you find the reason in the chapter for Bridged Networking.
https://www.virtualbox.org/manual/ch06.html#network_bridged