Linklocal service running on loopback address does not work
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Medium
|
Ashok Singh | |||
Trunk |
Fix Committed
|
Medium
|
Ashok Singh |
Bug Description
Following scenario does not work for linklocal services,
1. A service run on each of the compute nodes (say port 2000)
2. Linklocal service is added with following,
service-ip = 169.254.169.1
service-port = 2000
fabric-
fabric-
The expectation in this case is, when VM access the linklocal service, it should be served by server running on local compute node.
The configuration does not work.
The following configuration works,
service-ip = 169.254.169.1
service-port = 2000
fabric-
fabric-
To support this scenario, contrail-
1. VRouter does not have route for loopback-ip (127.0.0.1). So, packet gets forwarded according to default route
2. Even if we add route for 127.0.0.1 and point to vhost0, the host-os may discard the packets since loopback ip may is not expected on vhost0 interface
3. Better solution will be for agent to identify that service is running on loopback and add NAT rules such that packet is translated to vhost0 IP instead of loopback-ip.
Changed in juniperopenstack: | |
importance: | Undecided → Medium |
milestone: | none → r2.30-fcs |
Changed in juniperopenstack: | |
assignee: | Hari Prasad Killi (haripk) → Ashok Singh (ashoksr) |
Review in progress for https:/ /review. opencontrail. org/12126
Submitter: Ashok Singh (<email address hidden>)