How are you bridging your KVMs onto public IP space
The title says it all- there are a few different trains of thought about bridging KVMs onto public IP space. One of the most common I have seen use a local private bridge between the host and KVM client, and then a secondary assigned IP to the KVM itself.
Personally, I'd prefer the IP by itself, but I'm having problems getting it to work- I've aliased the entire /29 onto the br0 interface (with the primary IP for the host itself), and did an installation with the built-in dhcp bridging in QEMU- but can't quite get it to work with only a public IP. I've set it up as the native /29 with both host IP, and actual gateway- and I can ping when I go through the gateway, but seem to be blocked on the return path, even with the host set to forward packets for the client.
This is a semi-stock Debian Jessie, with a recent QEMU build from backports. How'd you do yours- and what lead you to figuring it out?
iWSS is now available in 3 sizes: 12MB ($599) ·13MB ($649) · 128GB ($799) - #DontTalkAboutLETClub