openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #25361
[Quantum] routing does not work as expected after quantum-linux-bridge sets up default route
Hi,
We are running OpenStack Folsom on CentOS 6.4.
Quantum-linuxbridge-agent is used.
Its external network is configured to use VLAN 83 and
its address range is 10.12.83.0/24.
The IP of the Quantum node is 10.12.183.11/24.
The problem is that after reboot, the quantum node cannot
connect to DNS servers (10.12.81.39) for a while (sometime tens of minutes).
After boot-up but before the quantum-linuxbridge-agent starts, the default gw is:
default 10.12.183.1 0.0.0.0 UG 0 0 0 eth2.183
With the gw, Quantum can get proper data from MySQL server
and RabbitMQ server using DNS server.
Quantum sets up a bridge on eth2.83 and make it a default gateway (10.12.83.1).
Now, there are two gateways:
default 10.12.83.1 0.0.0.0 UG 0 0 0 qg-49ff6d2f-a7
default 10.12.183.1 0.0.0.0 UG 0 0 0 eth2.183
The physical router 10.12.83.1 is configured to route for DNS servers.
But even with the updated routing table, when I do 'traceroute' DNS server,
it routes through 10.12.183.1.
And it cannot reach DNS server.
When I remove 10.12.183.1 entry from the routing table, it works fine.
But, I think it should work as it is because 10.12.183.1 is lower than 10.12.83.1 in
the routing table.
What could be wrong?
I will appreciate any help.
Thanks,
David
--
----------------------
Dr. Dong-In "David" Kang
Computer Scientist
USC/ISI