Hi all!
I have a basic environment with two nodes (one controller and one
compute).
My environment works well for the moment unless from the fact that I
cannot directly access the controller from any VM and vice versa.
My VMs are getting IPs from the 10.0.0.0/24 flat network which is
bridged with the 192.168.0.0/24 network that the controller is using
br100.
Here is the routing table from the compute node:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
153.5.5.128 0.0.0.0 255.255.255.128 U 0 0 0
eth0
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
br100
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
br100
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
virbr0
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0
eth1
0.0.0.0 153.5.5.129 0.0.0.0 UG 0 0 0
eth0
and the routing table from the VM:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0
eth0
0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0
eth0
If I try to ping the controller from the VM I am getting the following
result:
# ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
From 10.0.0.1: icmp_seq=2 Redirect Host(New nexthop: 192.168.0.10)
From 10.0.0.1: icmp_seq=3 Redirect Host(New nexthop: 192.168.0.10)
From 10.0.0.1: icmp_seq=4 Redirect Host(New nexthop: 192.168.0.10)
^C
--- 192.168.0.10 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3919ms
Similarly I cannot access the VM from the controller on the 10.0.0.0/24
network but only from the compute node.
I am using nova legacy networking mostly because I do need the
auto-assignment of floating IPs.
Any ideas are mostly welcomed.
Best,
George
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
