← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1450102] [NEW] neutron uses floating ips for on qrouter

 

Public bug reported:

Hi all..

Scenario:

stack@controller:~$ nova --version
2.19.0
stack@network:~$ neutron --version
2.3.8

Test tenant has one running test-instance with one test network (internal-net) and one internal-subnet (belonging to internal-net) has one router (test-router - qrouter-679e3d17-4e4f-42f8-b8c4-d76b38c565f7).  
The test-router has "ext-net"  set as gateway. 

ext-net and ext-subnet create as follows:
neutron net-create ext-net --router:external True --provider:physical_network external --provider:network_type flat
neutron subnet-create ext-net --name ext-subnet --allocation-pool start=A.B.C.147,end=A.B.C.158 --disable-dhcp --gateway A.B.C.146 A.B.C.0/24


Expected: 
A.B.C.147 floating IP to be allocated to the tenant project.

What happens:
A.B.C.148 floating IP is allocated to the tenant project.
A.B.C.147 was set on test-router (qrouter-679e3d17-4e4f-42f8-b8c4-d76b38c565f7)

root@network:~# ip netns exec qrouter-679e3d17-4e4f-42f8-b8c4-d76b38c565f7 ifconfig qg-8f04a366-ef
qg-8f04a366-ef Link encap:Ethernet  HWaddr fa:16:3e:6d:45:e2
          inet addr:A.B.C.147  Bcast:A.B.C.255  Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fe6d:45e2/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:69 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6577 (6.5 KB)  TX bytes:5296 (5.2 KB)


I consider it a bug because routers could be set to use other ips from the network A.B.C.0/24 which are not in the A.B.C.147-A.B.C.158 range (the floating ip range). The floating ip range should be exclusively used by virtual machines in cases where the CIDR defined is larger.
It's also bad because A.B.C.147 is routable and packets coming to A.B.C.147 from world will end up on my qrouter ;/

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  neutron uses floating ips for on qrouter

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Hi all..

  Scenario:

  stack@controller:~$ nova --version
  2.19.0
  stack@network:~$ neutron --version
  2.3.8

  Test tenant has one running test-instance with one test network (internal-net) and one internal-subnet (belonging to internal-net) has one router (test-router - qrouter-679e3d17-4e4f-42f8-b8c4-d76b38c565f7).  
  The test-router has "ext-net"  set as gateway. 

  ext-net and ext-subnet create as follows:
  neutron net-create ext-net --router:external True --provider:physical_network external --provider:network_type flat
  neutron subnet-create ext-net --name ext-subnet --allocation-pool start=A.B.C.147,end=A.B.C.158 --disable-dhcp --gateway A.B.C.146 A.B.C.0/24

  
  Expected: 
  A.B.C.147 floating IP to be allocated to the tenant project.

  What happens:
  A.B.C.148 floating IP is allocated to the tenant project.
  A.B.C.147 was set on test-router (qrouter-679e3d17-4e4f-42f8-b8c4-d76b38c565f7)

  root@network:~# ip netns exec qrouter-679e3d17-4e4f-42f8-b8c4-d76b38c565f7 ifconfig qg-8f04a366-ef
  qg-8f04a366-ef Link encap:Ethernet  HWaddr fa:16:3e:6d:45:e2
            inet addr:A.B.C.147  Bcast:A.B.C.255  Mask:255.255.255.0
            inet6 addr: fe80::f816:3eff:fe6d:45e2/64 Scope:Link
            UP BROADCAST RUNNING  MTU:1500  Metric:1
            RX packets:69 errors:0 dropped:0 overruns:0 frame:0
            TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0
            RX bytes:6577 (6.5 KB)  TX bytes:5296 (5.2 KB)

  
  I consider it a bug because routers could be set to use other ips from the network A.B.C.0/24 which are not in the A.B.C.147-A.B.C.158 range (the floating ip range). The floating ip range should be exclusively used by virtual machines in cases where the CIDR defined is larger.
  It's also bad because A.B.C.147 is routable and packets coming to A.B.C.147 from world will end up on my qrouter ;/

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


Follow ups

References