← Back to team overview

openstack team mailing list archive

Re: quantum: no gateways in network node

 

Hi Liu,

Have you done the below step? which actually attaches the router with the
specified network,

quantum router-interface-add $router_id $net1_ID
quantum router-interface-add $router-id $net2_ID


Regards,
Ashok


On Mon, May 6, 2013 at 3:02 PM, Liu Wenmao <marvelliu@xxxxxxxxx> wrote:

> Hi list:
>
> I set up quantum without namespace support, quantum-server/l3 agent/dhcp
> agent are running at the same node, besides there is a compute node.
>
> I create a router connecting two network(100.0.0.0/24, 200.0.0.0/24), so
> there should be two gateways(100.0.0.1 and 200.0.0.1) in the controller,
> however,I can see two dhcp server(100.0.0.3 and 200.0.0.2), but no gateways:
>
> root@controller:~# ifconfig
> br-ex...................
> br-int...................
> eth0...............
> eth1............
> eth2.............
> lo.................
> tap09a002af-66 Link encap:Ethernet  HWaddr fa:16:3e:9e:11:e0
>           inet addr:192.168.19.129  Bcast:192.168.19.255
>  Mask:255.255.255.128
>           inet6 addr: fe80::f816:3eff:fe9e:11e0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:146 errors:0 dropped:146 overruns:0 frame:0
>           TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:9490 (9.4 KB)  TX bytes:594 (594.0 B)
> tap160480aa-84 Link encap:Ethernet  HWaddr fa:16:3e:54:77:83
>           inet addr:100.0.0.3  Bcast:100.0.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::f816:3eff:fe54:7783/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1110 errors:0 dropped:156 overruns:0 frame:0
>           TX packets:514 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:121029 (121.0 KB)  TX bytes:66549 (66.5 KB)
>
> tap5b5891ac-94 Link encap:Ethernet  HWaddr fa:16:3e:ae:35:d3
>           inet addr:200.0.0.2  Bcast:200.0.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::f816:3eff:feae:35d3/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:147 errors:0 dropped:146 overruns:0 frame:0
>           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:9816 (9.8 KB)  TX bytes:468 (468.0 B)
>
> root@controller:~# quantum subnet-show subnet1
> +------------------+----------------------------------------------+
> | Field            | Value                                        |
> +------------------+----------------------------------------------+
> | allocation_pools | {"start": "100.0.0.2", "end": "100.0.0.254"} |
> | cidr             | 100.0.0.0/24                                 |
> | dns_nameservers  |                                              |
> | enable_dhcp      | True                                         |
> | gateway_ip       | 100.0.0.1                                    |
> | host_routes      |                                              |
> | id               | 25b34a57-db92-4a4f-a1f5-a550d5b8e1e6         |
> | ip_version       | 4                                            |
> | name             | subnet1                                      |
> | network_id       | eccf5627-a6c6-4007-82a0-f6b85bd2b4ce         |
> | tenant_id        | 53707d290204404dbff625378969c25c             |
> +------------------+----------------------------------------------+
>
> The VMs can not ping gateways, but can ping DHCP servers, why cannot I
> find the gateway?
>
>
> Wenmao Liu
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Regds,

Ashok ,
Delivery Consultant,
HP.

References