Open hoo29 opened 7 months ago
Is your feature request related to a problem? Please describe. In mirrored networking mode, traffic for any virtual interfaces libvirt creates is not routable from Windows.
To reproduce:
Vagrantfile
Vagrant.configure("2") do |config| config.vm.box = "rockylinux/9" config.vm.provision "shell", inline: """ dnf install httpd -y systemctl start httpd systemctl enable httpd echo $(ip addr show eth0 | grep inet | awk '{print $2}' | cut -d/ -f1) """ end
vagrant up --provider=libvirt
curl $THE_IP
Describe the solution you'd like Routes created for libvirt virtual interfaces to be routable from Windows.
Describe alternatives you've considered Using chrome installed in WSL works around the problem.
Additional context route print on Windows does not show any routes for the virbrX interfaces libvirt creates.
route print
Is there any updates on whether this is being considered or if there are potential alternative solutions?
Is your feature request related to a problem? Please describe. In mirrored networking mode, traffic for any virtual interfaces libvirt creates is not routable from Windows.
To reproduce:
Vagrantfile
in a directory:vagrant up --provider=libvirt
. Note down the ipv4 address shown at the end of the provisioning output.curl $THE_IP
from WSL and you will get a response but you will not from windows.Describe the solution you'd like Routes created for libvirt virtual interfaces to be routable from Windows.
Describe alternatives you've considered Using chrome installed in WSL works around the problem.
Additional context
route print
on Windows does not show any routes for the virbrX interfaces libvirt creates.