So this is how i want to do this:

• Devices in my network can interact with the VM as if it was another computer, mainly for testing with jellyfin, caddy, dns (pihole)
• It can be done on a wireless interface
• The VM has a wireless
• The virtual interface uses dhcp

i am indeed that fucking stupid holy shit.

Ok so it now works and with internet access too! with the exception of my host pc, i can't ping my router form my host no more and ports are still not working on the host and honestly im not gonna bother, im probably going to route ssh through a unix socket and be done with it.
I also stopped using dhcpcd because i'm to lazy to sync the vm ip and the host ipvtap ip

finally have time for this again

got the interface for host-vm communication up and running with the libvirt nat bridge, i mean i have it at hand why not use it? (this totally wont come back to torment me).

Weird thing is that by using -netdev bridge... qemu doesn't assign an ip to the tap in the host and idk if it is a requirement cuz i did setup the ipvtap interface with an ip on the host and an ip on the vm.
Idk how qemu sets up the tap interface behind scenes, maybe because of iptables shenanigans and the NAT thing

Can someone explain how it works? I guess not having an IP on the host tap interface makes more sense than having one

#networking #qemu #kvm