Revision history [back]

click to hide/show revision 1
initial version

It seems the problem then should be researched into host networking. It seems that you're using the same IP address space for management and data network.

This might confuse the network node, as it would not know where the packets need to be forwarded. For instance a packet to www.google.com might be sent either to qg-xxxx or eth0. I think you always want it forwarded to qg-xxxx.

This is evident from your routing table:

route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface PublicIP.0 0.0.0.0 255.255.255.0 U 0 0 0 qg-6ad484d8-33 PublicIP.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 qr-d2665361-33 0.0.0.0 PublicIP.1 0.0.0.0 UG 0 0 0 qg-6ad484d8-33 0.0.0.0 PublicIP.1 0.0.0.0 UG 0 0 0 eth0

I totally understand you are not able to partition the public address space. It's already a good thing your advisor gave you a few to play with. Perhaps moving your management network to a private address space (something like 192.168.0.0/24) might be a good solution.

This might also explain why the public IP can't be pinged anymore after you start the l3 agent.