Note: OVS from before 1.5, which includes the default versions shipped with 12.04 and Fedora 17, has a bug that causes it not to work correctly with floating IPs when the person contacting the floating IP is on the same box as quantum-l3-agent.
While not very likely to happen in a production setup, this is fairly common in simple development environments. For example, let's say you create an external network 40.0.0.0/24 for floating IPs. If you then assign br-ex the IP 40.0.0.1, you should be able to reach all of your VMs with floating IPs, but it won't work because of this bug. Oddly, it will often appear to work if you use ping, but in reality you are pining the IP address in the router namespace, not the VM.
We believe the following OVS commit it required for this to work properly:
We are looking at creating a new stable release on the 1.4.x branch to include this change and plan to work with distros to get it pulled into their packages.
Note: OVS from before 1.5, which includes the default versions shipped with 12.04 and Fedora 17, has a bug that causes it not to work correctly with floating IPs when the person contacting the floating IP is on the same box as quantum-l3-agent.
While not very likely to happen in a production setup, this is fairly common in simple development environments. For example, let's say you create an external network 40.0.0.0/24 for floating IPs. If you then assign br-ex the IP 40.0.0.1, you should be able to reach all of your VMs with floating IPs, but it won't work because of this bug. Oddly, it will often appear to work if you use ping, but in reality you are pining the IP address in the router namespace, not the VM.
We believe the following OVS commit it required for this to work properly:
http:// openvswitch. org/cgi- bin/gitweb. cgi?p=openvswit ch;a=commitdiff ;h=53e6421bc839 18ac2d00ba5516f 205fa7e394140
We are looking at creating a new stable release on the 1.4.x branch to include this change and plan to work with distros to get it pulled into their packages.