search for: virbr2_nic

...ttps://www.redhat.com/archives/libvir-list/2013-September/msg01311.html but I suppose it is not exactly that thing. I've already figured the source of trouble is anyway related to these rules added: -A POSTROUTING -o br0 -j MASQUERADE -A POSTROUTING -o enp0s25 -j MASQUERADE -A POSTROUTING -o virbr2_nic -j MASQUERADE -A POSTROUTING -o vnet0 -j MASQUERADE Here, virbr2_nic and vnet0 are used by libvirt for arranging network configurations for VMs, ok. However, br0 is a main interface of this host with primary ip address, with enp0s25 being a physical nic of this host, and it is used for all sort...

Hi Daniel and Laine, [...] >> -A POSTROUTING -o br0 -j MASQUERADE >> -A POSTROUTING -o enp0s25 -j MASQUERADE >> -A POSTROUTING -o virbr2_nic -j MASQUERADE >> -A POSTROUTING -o vnet0 -j MASQUERADE > > *None* of those rules were added by libvirt (unless your build of [...] > You can verify my "counter-claim" by running "virsh net-destroy" for all > of your libvirt networks, and seeing that the offendi...

...st/2013-September/msg01311.html > but I suppose it is not exactly that thing. > > I've already figured the source of trouble is anyway related to these > rules added: > > -A POSTROUTING -o br0 -j MASQUERADE > -A POSTROUTING -o enp0s25 -j MASQUERADE > -A POSTROUTING -o virbr2_nic -j MASQUERADE > -A POSTROUTING -o vnet0 -j MASQUERADE *None* of those rules were added by libvirt (unless your build of libvirt, in addition to being ancient, has also been heavily hacked by a third party with downstream-only patches, although I can't imagine how the rules you show could...