search for: kvm2

...nderstanding of how things work. I have a kvm hypervisor host (KVM1) with two physical Ethernet nics configured as bridges (br0 and br1). KVM1 br0 is configured with a public ipv4 address [x.y.z.42/24] and br1 is configured with a private ipv4 address [192.168.216.42/24]. A second kvm hypervisor, KVM2, is similarly configured albeit with different IPv4 addresses of course. Packet forwarding is enabled on both hypervisor hosts and both have IPTABLES configured, albeit not for masquerading. Guest systems on each of the two kvm hosts are also configured with two virtual nics, eth0 and eth1, mapped...

I'm using director on dovecot 2.0 At present, I know that two instances are connected, If I stop of one system, then I can watch how to the connections are closed on port 5000. I defined 5000 as director port. I have one user (user1) connected to kvm1 (192.168.13.100) and kvm2 (192.168.13.101) servers v?a telnet telnet kvm1 143 and then login telnet kvm2 143 and then login If try to execute doveadm director status I can watch the two server like that: [root at kvm1 ~]# doveadm director status mail server ip vhosts users 192.168.13.100...

...-----------------------+ br1 br2 +--------------------------------- | | | | | | | | Client A +---------------+ Client B (hosts KVM1, KVM2, etc) Each client uses the bridge's IP address on the same side as default gateway. Client A can successfully ping or ssh (for example) to a KVM machine by IP address by using the KVM machine's net1 IP address. Client B can likewise communicate using the KVM machine's net2 IP addres...

Hi, I have a KVM server running on Centos 7.5. [root at kvm2 ~]# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core) Qemu packages are from Centos repository. [root at kvm2 ~]# rpm -qa|grep qemu libvirt-daemon-driver-qemu-3.9.0-14.el7_5.7.x86_64 qemu-img-1.5.3-156.el7_5.5.x86_64 qemu-kvm-common-1.5.3-156.el7_5.5.x86_64 ipxe-roms-qemu-20170123-1.gi...

...e According to a disucssion in IRC dnat (and snat) should be valid states for the connection tracking , so a rule like the following should actually work: ct state dnat accept Apparently this is already implemented. However, right now with nftables version 0.5 this results in an error: [root at kvm2 ~]# nft -f /etc/nftables.conf /etc/nftables.conf:115:18-21: Error: syntax error, unexpected dnat ct state dnat accept ^^^^ According to fw in the #netfilter IRC this is due to a parser ambiguity: <aborrero> kbabioch: that seems like a bug, I see support for it in the current...