yahoo-eng-team team mailing list archive

[gao yu <1901992@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Pre-conditions: After add a static route with 0.0.0.0/0 destination and nexthop 
is an internal network ip in case of DVR.

results:In the case of DVR the static routes for local internal router networks 
will be added to the snat_namespace and router_namespace.But there is already a 
default route with nexthop is external gateway ip, supporting VMs which did not 
binding a fip to go external.But after add  a static route with 0.0.0.0/0 destination, 
the new static route will replace the default route.

so I think neutron should not allow to create static routes with
0.0.0.0/0 destination.

** Affects: neutron
     Importance: Undecided
     Assignee: gao yu (gaoyublack)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => gao yu (gaoyublack)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1901992

Title:
  Destination 0.0.0.0/0 static route cause snat unable to go external

Status in neutron:
  New

Bug description:
  Pre-conditions: After add a static route with 0.0.0.0/0 destination and nexthop 
  is an internal network ip in case of DVR.

  results:In the case of DVR the static routes for local internal router networks 
  will be added to the snat_namespace and router_namespace.But there is already a 
  default route with nexthop is external gateway ip, supporting VMs which did not 
  binding a fip to go external.But after add  a static route with 0.0.0.0/0 destination, 
  the new static route will replace the default route.

  so I think neutron should not allow to create static routes with
  0.0.0.0/0 destination.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1901992/+subscriptions