I tried to boot a few VMs on the env Alexander provided, and see the following: - floating IPs work as expected: neutron router creates an interfaces, listens on the specified floating IP address, DNAT network traffic correctly - the problem is that VMs don't receive fixed IP leases: Initializing random number generator... done. Starting acpid: OK cirros-ds 'local' up at 6.59 no results found for mode=local. up 7.11. searched: nocloud configdrive ec2 Starting network... udhcpc (v1.20.1) started Sending discover... Sending discover... Sending discover... Usage: /sbin/cirros-dhcpc No lease, failing WARN: /etc/rc3.d/S40-network failed cirros-ds 'net' up at 188.54 checking http://169.254.169.254/2009-04-04/instance-id failed 1/20: up 188.82. request failed failed 2/20: up 191.39. request failed failed 3/20: up 193.64. request failed failed 4/20: up 195.82. request failed tcpdump on br-prv (on the compute node) shows there are no replies to DHCP requests: 07:52:23.587684 IP6 :: > ff02::1:ff64:489b: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe64:489b, length 24 07:52:23.588235 IP6 :: > ff02::1:ff64:489b: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe64:489b, length 24 07:52:23.588266 IP6 :: > ff02::1:ff64:489b: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe64:489b, length 24 07:52:23.588289 IP6 :: > ff02::1:ff64:489b: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe64:489b, length 24 07:52:23.675068 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:23.675724 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:23.675759 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:23.675773 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:24.584216 ARP, Request who-has 10.109.1.2 (Broadcast) tell 10.109.1.2, length 46 07:52:24.584362 ARP, Request who-has 10.109.1.2 (Broadcast) tell 10.109.1.2, length 46 07:52:24.584211 ARP, Request who-has 10.109.1.2 (Broadcast) tell 10.109.1.2, length 46 07:52:24.584469 ARP, Request who-has 10.109.1.2 (Broadcast) tell 10.109.1.2, length 46 07:52:25.087188 ARP, Reply 10.109.1.3 is-at 1e:33:1c:55:51:9f (oui Unknown), length 46 07:52:25.087205 ARP, Reply 10.109.1.3 is-at 1e:33:1c:55:51:9f (oui Unknown), length 46 07:52:25.087210 ARP, Reply 10.109.1.3 is-at 1e:33:1c:55:51:9f (oui Unknown), length 46 07:52:25.087256 ARP, Reply 10.109.1.3 is-at 1e:33:1c:55:51:9f (oui Unknown), length 46 At the same time I can see both requests and replies in dnsmasq logs: <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPDISCOVER(tap7452d06b-85) fa:16:3e:64:48:9b <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPOFFER(tap7452d06b-85) 192.168.111.12 fa:16:3e:64:48:9b <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPDISCOVER(tap7452d06b-85) fa:16:3e:64:48:9b <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPOFFER(tap7452d06b-85) 192.168.111.12 fa:16:3e:64:48:9b <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPDISCOVER(tap7452d06b-85) fa:16:3e:64:48:9b <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPOFFER(tap7452d06b-85) 192.168.111.12 fa:16:3e:64:48:9b <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPDISCOVER(tap7452d06b-85) fa:16:3e:64:48:9b <30>Jan 30 07:54:23 node-1 dnsmasq-dhcp[8851]: DHCPOFFER(tap7452d06b-85) 192.168.111.12 fa:16:3e:64:48:9b As well as in tcpdump log of a bond: 07:52:23.675101 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:23.675377 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:23.675557 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:23.675608 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:64:48:9b (oui Unknown), length 290 07:52:23.676888 IP 192.168.111.3.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 07:52:23.677048 IP 192.168.111.3.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 07:52:23.677265 IP 192.168.111.3.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 07:52:23.677266 IP 192.168.111.3.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 07:52:23.677268 IP 192.168.111.2.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 07:52:23.677410 IP 192.168.111.2.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 07:52:23.677412 IP 192.168.111.2.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 07:52:23.677548 IP 192.168.111.2.bootps > 192.168.111.12.bootpc: BOOTP/DHCP, Reply, length 328 It's not clear to me, why DHCP replies don't get through OVS to br-prv bridge.