Open Stack

Does eth1 reside on the same layer 2 network as 172.20.0.1? Did you disable
MAC address filtering on your hypervisors so frames with MAC addresses
other than the one known to the hypervisor on eth1 can pass through it?

On Tue, Oct 20, 2015 at 11:10 AM, Veselin Karamanski <veselin.k at gmail.com>
wrote:

> Hello Matt,
> Thank you for your answer and for your help.
> ​The router created following the official install guide for "Liberty" is
> not able to PING the external gateway /172.20.0.1/.
> The controller and compute nodes are KVM virtual machines. The IP
> 172.20.0.1 is virtual device on my server.
>
> These are the outputs I think might be useful for you to troubleshoot:
>
> -------
> root at controller:~# brctl show
> bridge name     bridge id               STP enabled     interfaces
> brq3c7797b4-ae          8000.5254007f5d7b       no              eth1
>                                                         tap3df2d29f-32
>                                                         tap99a437ce-78
> brq432a531d-9d          8000.164f7c17d942       no
>  tap31b69978-14
>                                                         tap6bb3b90d-2a
>                                                         vxlan-83
> ​​
> -------
> root at controller:~# ip netns
> qrouter-c8296613-4125-420f-af74-f7dc4240bbe4
> qdhcp-3c7797b4-aecb-4267-bbeb-2d5e25cfe9ef
> qdhcp-432a531d-9d4e-4613-8919-599f8a7df6b7
>
> root at controller:~# ip netns exec
> qrouter-c8296613-4125-420f-af74-f7dc4240bbe4 ifconfig
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
> ...
> qg-99a437ce-78 Link encap:Ethernet  HWaddr fa:16:3e:b6:c4:d0
>           inet addr:172.20.0.102  Bcast:172.20.0.255  Mask:255.255.255.0
> ...
>
> qr-31b69978-14 Link encap:Ethernet  HWaddr fa:16:3e:37:76:8c
>           inet addr:172.16.1.1  Bcast:172.16.1.255  Mask:255.255.255.0
> ...
>
> -------
>
> root at controller:~# ip netns exec
> qrouter-c8296613-4125-420f-af74-f7dc4240bbe4 ip r
> default via 172.20.0.1 dev qg-99a437ce-78
> 172.16.1.0/24 dev qr-31b69978-14  proto kernel  scope link  src
> 172.16.1.1
> 172.20.0.0/24 dev qg-99a437ce-78  proto kernel  scope link  src
> 172.20.0.102
>
> -------
>
> root at controller:~# ip netns exec
> qrouter-c8296613-4125-420f-af74-f7dc4240bbe4 ping 172.20.0.1
> PING 172.20.0.1 (172.20.0.1) 56(84) bytes of data.
> From 172.20.0.102 icmp_seq=1 Destination Host Unreachable
> ...
>
> -------
>
> root at controller:~# ping 172.20.0.1
> PING 172.20.0.1 (172.20.0.1) 56(84) bytes of data.
> 64 bytes from 172.20.0.1: icmp_seq=1 ttl=64 time=0.077 ms
> ^C
> --- 172.20.0.1 ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 0.077/0.077/0.077/0.000 ms
>
> ########################################################
>
>
> root at compute1:~# brctl show
> bridge name     bridge id               STP enabled     interfaces
> brq432a531d-9d          8000.767a4a107f5e       no
>  tap6c99f105-81
>                                                         vxlan-83
> ​#################################
>
>
>
>
>
> ​
>
> On Tue, Oct 20, 2015 at 6:16 PM Matt Kassawara <mkassawara at gmail.com>
> wrote:
>
>> I suspect that extension appeared in the list while updating the
>> installation guide using pre-release packages. I don't see it in my lab
>> environment with release packages. In any case, I don't think it is causing
>> your problem. Can you elaborate on "router is not able to see the public
>> network" and what troubleshooting steps you have taken for it?
>>
>> On Tue, Oct 20, 2015 at 8:21 AM, Veselin Karamanski <veselin.k at gmail.com>
>> wrote:
>>
>>> Hello All,
>>> Following the Liberty installation Guide I've successfully installed it
>>> but got stuck at this check:
>>>
>>>
>>> http://docs.openstack.org/liberty/install-guide-ubuntu/neutron-verify.html
>>>
>>> ...where after executing  "neutron ext-list" command I found that the
>>> row bellow is missing:
>>>
>>> | address-scope         | Address scope                               |
>>>
>>> I choose "Networking Option 2: Self-service networks" to build my
>>> OpenStack and now the router is not able to see the public network. I dont
>>> know if this is related to missing "address-scope" extension. Everything is
>>> double checked so could you help me with any ideas how to fix that.
>>>
>>> This is not my first Openstack installation.
>>>
>>> Thank you in advance for your time and help.
>>>
>>> Veselin Karamanski
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20151020/d28c9ae5/attachment.html>