Open Stack

Namespace router's iptables:
--------------------------------------------
# ip netns exec qrouter-27b3117b-1fe7-43b6-a1af-6c4cd54387bb iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
quantum-l3-agent-INPUT  all  --  anywhere anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
quantum-filter-top  all  --  anywhere anywhere
quantum-l3-agent-FORWARD  all  --  anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
quantum-filter-top  all  --  anywhere anywhere
quantum-l3-agent-OUTPUT  all  --  anywhere anywhere

Chain quantum-filter-top (2 references)
target     prot opt source               destination
quantum-l3-agent-local  all  --  anywhere anywhere

Chain quantum-l3-agent-FORWARD (1 references)
target     prot opt source               destination

Chain quantum-l3-agent-INPUT (1 references)
target     prot opt source               destination

Chain quantum-l3-agent-OUTPUT (1 references)
target     prot opt source               destination

Chain quantum-l3-agent-local (1 references)
target     prot opt source               destination
root at controller-desktop:/home/controller#


On Monday 26 November 2012 12:41 PM, Igor Laskovy wrote:
>
> Please give to us your iptables -L
>
> Igor Laskovy
> facebook.com/igor.laskovy <http://facebook.com/igor.laskovy>
> Kiev, Ukraine
>
> On Nov 24, 2012 7:02 PM, "Shyam Goud" <shyam.todeti at oneconvergence.com 
> <mailto:shyam.todeti at oneconvergence.com>> wrote:
>
>     Oleg,
>
>     It shows the ip_forward flag enabled.
>
>     # ip netns exec qrouter-f3554f15-78c0-4402-8df5-55ebb8da3f4c
>     sysctl net.ipv4.ip_forward
>     net.ipv4.ip_forward = 1
>
>     Thanks,
>
>     On Saturday 24 November 2012 12:51 PM, Oleg Gelbukh wrote:
>>     Hello,
>>
>>     Just to make sure, what is ip_forward set to on the router?
>>
>>     --
>>     Oleg Gelbukh
>>     Sr. IT Engineer,
>>     Mirantis IT
>>
>>
>>     On Fri, Nov 23, 2012 at 4:33 PM, Shyam Goud
>>     <shyam.todeti at oneconvergence.com
>>     <mailto:shyam.todeti at oneconvergence.com>> wrote:
>>
>>         All,
>>
>>         Under one Tenant created 1 network with 2 subnets
>>         [10.10.10.0/24 <http://10.10.10.0/24> and
>>         20.20.20.0/24 <http://20.20.20.0/24>] and 1 Router with 2
>>         interfaces attached to corresponding
>>         subnets.
>>
>>         1. Ping b/w same subnet VMs successful.
>>         2. Ping to all Router/DHCP (10.10.10.1 & 2/20.20.20.1
>>         <http://20.20.20.1> & 2) from both
>>         subnet VMs is successful
>>         3. Ping across subnet VMs fails.
>>
>>         Am I missing something here, to reach across subnets ?
>>
>>         ++++++++++++ Router's routing table +++++++++++++
>>         controller-desktop:~# ip netns exec
>>         qrouter-f3554f15-78c0-4402-8df5-55ebb8da3f4c route -n
>>         Kernel IP routing table
>>         Destination     Gateway         Genmask Flags Metric Ref Use
>>         Iface
>>         10.10.10.0      0.0.0.0         255.255.255.0   U   0 0        0
>>         qr-ff10b98d-55
>>         20.20.20.0      0.0.0.0         255.255.255.0   U   0 0        0
>>         qr-c5c00091-e4
>>         root at controller-desktop:~#
>>         +++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>         Thanks,
>>         Shyam.
>>
>>
>>
>>
>>
>>         _______________________________________________
>>         OpenStack-operators mailing list
>>         OpenStack-operators at lists.openstack.org
>>         <mailto:OpenStack-operators at lists.openstack.org>
>>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
>
>     _______________________________________________
>     OpenStack-operators mailing list
>     OpenStack-operators at lists.openstack.org
>     <mailto:OpenStack-operators at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121126/92bcb52e/attachment.html>