Hi, >Thanks for the response. I'm beginning to think that my strategy here >is all wrong to begin with. Here's why: >1. The subnet for my VMs is 192.168.122.0/24. This is created by >libvirtd when it starts up. >2. I start up Firefox in a VM, then go to google.com. >3. As I watch with tcpdump, I never even see 192.168.122.x in the >output. >Maybe libvirtd is doing its own network voodoo before handing off to >the kernel network stack. Sorry, I've never used libvirtd, but if your virtualization backend is kvm and it's configured for "userspace networking", iptables won't do what you want. > [Shrug] Should I expect tcpdump to show >packets coming through a bridge (virbr0 or just br0)? In "bridged networking" you should see packets on VMs interface (tapX) and bridge interface (brX). Try setting it up. This page may be of some help: http://wiki.libvirt.org/page/Networking Best regards, Marek -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
