192.168.19.129 is the gateway ip for the pub subnet 61897e3b-ea17-4848-a2e0-e0847cef4b2e. This is a default gateway ip since u does not give one when creating this subnet. 192.168.19.130 is the ip of qg-0eda5152-09 192.168.19.129 should be one IP somewhere in your physical router.
** Changed in: quantum Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to quantum. https://bugs.launchpad.net/bugs/1167683 Title: wrong quantum gateway set Status in OpenStack Quantum (virtual network service): Invalid Bug description: I setup quantum grizzly use dhcp- and l3-agent with namespace enabled. After I create a router with 2 subnets and 1 public nets, I find that vms can not ping Internet hosts. I use the following command to create a public sub-network: quantum subnet-create public 192.168.19.129/25 root@controller:~# quantum router-list +--------------------------------------+---------+--------------------------------------------------------+ | id | name | external_gateway_info | +--------------------------------------+---------+--------------------------------------------------------+ | 7bde1209-e8ed-4ae6-a627-efaa148c743c | router1 | {"network_id": "5cb82ea6-956c-44bb-adaf-b522f0f0c003"} | +--------------------------------------+---------+--------------------------------------------------------+ root@controller:~# quantum subnet-list +--------------------------------------+------+-------------------+------------------------------------------------------+ | id | name | cidr | allocation_pools | +--------------------------------------+------+-------------------+------------------------------------------------------+ | 5d8ba8f6-7339-44a0-95ca-891aab144aeb | | 200.0.0.0/24 | {"start": "200.0.0.2", "end": "200.0.0.254"} | | 61897e3b-ea17-4848-a2e0-e0847cef4b2e | | 192.168.19.129/25 | {"start": "192.168.19.130", "end": "192.168.19.254"} | | c11eaa0d-3aff-41a8-909a-1dfdfdf20f48 | | 100.0.0.0/24 | {"start": "100.0.0.2", "end": "100.0.0.254"} | +--------------------------------------+------+-------------------+------------------------------------------------------+ root@controller:~# quantum net-list +--------------------------------------+--------+--------------------------------------------------------+ | id | name | subnets | +--------------------------------------+--------+--------------------------------------------------------+ | 17d31ea4-4473-4da0-9493-9a04fa5aff33 | net1 | c11eaa0d-3aff-41a8-909a-1dfdfdf20f48 100.0.0.0/24 | | 29b70469-db85-44fa-b5fd-d14d63ac2ef9 | net2 | 5d8ba8f6-7339-44a0-95ca-891aab144aeb 200.0.0.0/24 | | 5cb82ea6-956c-44bb-adaf-b522f0f0c003 | public | 61897e3b-ea17-4848-a2e0-e0847cef4b2e 192.168.19.129/25 | +--------------------------------------+--------+--------------------------------------------------------+ root@controller:~# ip netns exec qrouter-7bde1209-e8ed-4ae6-a627-efaa148c743c ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:45 errors:0 dropped:0 overruns:0 frame:0 TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4803 (4.8 KB) TX bytes:4803 (4.8 KB) qg-0eda5152-09 Link encap:Ethernet HWaddr fa:16:3e:7a:a1:9f inet addr:192.168.19.130 Bcast:192.168.19.255 Mask:255.255.255.128 inet6 addr: fe80::f816:3eff:fe7a:a19f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8191 errors:0 dropped:0 overruns:0 frame:0 TX packets:6750 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:935028 (935.0 KB) TX bytes:283716 (283.7 KB) qr-8af2e01f-bb Link encap:Ethernet HWaddr fa:16:3e:f7:3d:5e inet addr:100.0.0.1 Bcast:100.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fef7:3d5e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8541 errors:0 dropped:0 overruns:0 frame:0 TX packets:7563 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1034980 (1.0 MB) TX bytes:904654 (904.6 KB) qr-9b9a3229-19 Link encap:Ethernet HWaddr fa:16:3e:66:13:08 inet addr:200.0.0.1 Bcast:200.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe66:1308/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1931 errors:0 dropped:0 overruns:0 frame:0 TX packets:47 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:609478 (609.4 KB) TX bytes:4805 (4.8 KB) The public interface is 192.168.19.130, not 192.168.19.129. So after I assigned a floating ip(192.168.19.131) for a vm X(100.0.0.4), X can ping 192.168.19.130 but cannot ping 8.8.8.8. I check the route table: root@controller:~# ip netns exec qrouter-7bde1209-e8ed-4ae6-a627-efaa148c743c route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.19.129 0.0.0.0 UG 0 0 0 qg-0eda5152-09 100.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 qr-8af2e01f-bb 192.168.19.128 0.0.0.0 255.255.255.128 U 0 0 0 qg-0eda5152-09 200.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 qr-9b9a3229-19 So I change the gateway from 192.168.19.129 to 192.168.19.130, then VM can ping outside host. I don't know why the gateway is set as 192.168.19.129, maybe there is some conflicts? To manage notifications about this bug go to: https://bugs.launchpad.net/quantum/+bug/1167683/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp