Ubuntu mainline 2453: Kernel route lookup failing for SNAT
Bug #1392260 reported by
Sandip Dey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Committed
|
Undecided
|
Divakar Dharanalakota | ||
R2.0 |
Fix Committed
|
Undecided
|
Divakar Dharanalakota |
Bug Description
scripts.
Agent has the default root, but kernel route lookup failing, while trying to ping 8.8.8.8 from private vm
Naveen debugged it
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
assignee: | Naveen N (naveenn) → Sachin Bansal (sbansal) |
Changed in juniperopenstack: | |
assignee: | Sachin Bansal (sbansal) → Divakar Dharanalakota (ddivakar) |
To post a comment you must log in.
Sachin,
Setup nodea11 is in same state .. Please take a look.
Not sure if Naveen got a chance to talk to you. They debugged that the
problem was that the acl in agent was having a wrong protocol number since
schema did not set the protocol field at all
http:// nodea11: 8083/Snh_ IFMapTableShowR eq?table_ name=
<vrf-assign-table> condition> </protocol> ip-prefix> 10.204. 219.186< /ip-prefix> ip-prefix- len>32< /ip-prefix- len> network> </virtual- network> group>< /security- group> policy> </network- policy>
<vrf-assign-rule>
<match-
<protocol>
<src-address>
<subnet>
<
<
</subnet>
<virtual-
<security-
<network-
</src-address>