Unable to communicate to floatingip on a same network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Itsuro Oda |
Bug Description
If one try to communicate from a tenant network to floatingip which attached to
a port on the same network, the communication fails.
-------
for example, unable to communicate from 10.0.0.3 to 100.0.0.5
-----
| 100.0.0.0/24
+----+----+
| router |
+----+----+
| 10.0.0.0/24
--+--
| |
10.0.0.3 10.0.0.4
-------
Note that ping is not adequate to check connection.
icmp reply is returned thus ping success but the from address is different.
---
<10.0.0.3 host>: $ ping 100.0.0.5
PING 100.0.0.5 (100.0.0.5) 56(84) bytes of data.
64 bytes from 10.0.0.4: icmp_seq=1 ttl=64 time=3.45 ms (must be returned from 100.0.0.5)
---
(This is because destination address (100.0.0.5) is DNATed to fixed ip (10.0.0.4)
on the router, but reply does not go through the router.)
Use TCP/IP (ex. ssh) to check connection.
This problem is a regression cased by https:/
(it is my fault.)
This maybe not common use case but should be fixed since it was OK before the patch.
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
assignee: | nobody → Itsuro Oda (oda-g) |
Changed in neutron: | |
milestone: | none → kilo-rc1 |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-rc1 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/161947
Review: https:/