Re: [Openstack] question on the GRE Communication

2013-03-15 Thread Aru s
Thanks Robert.

On Thu, Mar 14, 2013 at 7:25 PM, Robert van Leeuwen <
robert.vanleeu...@spilgames.com> wrote:

> > Thanks for the reply. I have one more question.
> > How we will check whether the tunneling is established or not?
>
> tcpdump can show you the GRE traffic:
> tcpdump -i ethX proto gre
>
> Cheers,
> Robert
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] question on the GRE Communication

2013-03-15 Thread Aru s
Thanks Logan

On Thu, Mar 14, 2013 at 7:16 PM, Logan McNaughton wrote:

> I'm not sure about verifying the GRE tunnels, so I can't be much help
> there.
>
> As far as understanding how the tunneling happens, GRE is an open
> protocol, not specific to OpenStack, or any vendor, and googling GRE should
> give you plenty of information about it.
> On Mar 14, 2013 5:21 AM, "Aru s"  wrote:
>
>> Hi  Logan,
>>
>> Thanks for the reply. I have one more question.
>> How we will check whether the tunneling is established or not?
>> I have gone through lot of documents of gre setup and all are says that
>> the "ovs-vsctl show" command will show the tunnel info.
>> Also is there a doc to understand how the magic happens for tunneling.
>>
>> Regards,
>> Arumon
>>
>>
>> On Tue, Mar 12, 2013 at 6:23 PM, Logan McNaughton wrote:
>>
>>> For Quantum GRE tunneling, the network node and compute nodes need a NIC
>>> on your data network. You assign each of those NIC's an IP (for instance,
>>> 192.168.1.1-3). Then (assuming you are using openvswitch with GRE
>>> tunneling) you set up your quantum configs. Look at the Quantum
>>> administration guide for an example of GRE tunneling with openvswitch.
>>>
>>> After that you just let it work its magic. All VM traffic is
>>> encapsulated inside GRE packets traveling between the nodes, it'll all look
>>> like packets in that 192.168.1-3 network.
>>>
>>> Once the packet reaches its destination node, the GRE encapsulation is
>>> removed and the VM packet is read.
>>> On Mar 12, 2013 6:36 AM, "Aru s"  wrote:
>>>
  Hi,

 I am trying to configuring openstack with one controller and one
 network and two compute nodes.
 I am not able to understand how the communication of the VM's happens
 which are for the same tenant with same ip range but on the different
 compute hosts.
 Please help me to understand how GRE communication happens.

 Regards,
 Arumon

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


>>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] question on the GRE Communication

2013-03-14 Thread The King in Yellow
That's the best way I found to see if GRE is up, just watching for two way
"proto gre" traffic.

Here's how you can match the IP addresses *inside* the GRE packet, which
you probably will want.  Note that 0x0a050505 is hexadecimal for my desired
IP address of 10.5.5.5:

root@os-network:~# tcpdump -i eth1 'proto gre and ( ip[58:4] = 0x0a050505
or ip[62:4] = 0x0a050505 )'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
16:18:17.434378 IP os-network-d > os-compute-01-d: GREv0, key=0x0, length
110: IP opskzlp119.snops.net > 10.5.5.5: ICMP echo request, id 21321, seq
488, length 64
16:18:17.436190 IP os-compute-01-d > os-network-d: GREv0, key=0x0, length
110: IP 10.5.5.5 > opskzlp119.snops.net: ICMP echo reply, id 21321, seq
488, length 64
16:18:18.435750 IP os-network-d > os-compute-01-d: GREv0, key=0x0, length
110: IP opskzlp119.snops.net > 10.5.5.5: ICMP echo request, id 21321, seq
489, length 64
16:18:18.437798 IP os-compute-01-d > os-network-d: GREv0, key=0x0, length
110: IP 10.5.5.5 > opskzlp119.snops.net: ICMP echo reply, id 21321, seq
489, length 64
:


On Thu, Mar 14, 2013 at 9:55 AM, Robert van Leeuwen <
robert.vanleeu...@spilgames.com> wrote:

> > Thanks for the reply. I have one more question.
> > How we will check whether the tunneling is established or not?
>
> tcpdump can show you the GRE traffic:
> tcpdump -i ethX proto gre
>
> Cheers,
> Robert
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] question on the GRE Communication

2013-03-14 Thread Robert van Leeuwen
> Thanks for the reply. I have one more question.
> How we will check whether the tunneling is established or not?

tcpdump can show you the GRE traffic:
tcpdump -i ethX proto gre

Cheers,
Robert
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] question on the GRE Communication

2013-03-14 Thread Logan McNaughton
I'm not sure about verifying the GRE tunnels, so I can't be much help there.

As far as understanding how the tunneling happens, GRE is an open protocol,
not specific to OpenStack, or any vendor, and googling GRE should give you
plenty of information about it.
On Mar 14, 2013 5:21 AM, "Aru s"  wrote:

> Hi  Logan,
>
> Thanks for the reply. I have one more question.
> How we will check whether the tunneling is established or not?
> I have gone through lot of documents of gre setup and all are says that
> the "ovs-vsctl show" command will show the tunnel info.
> Also is there a doc to understand how the magic happens for tunneling.
>
> Regards,
> Arumon
>
>
> On Tue, Mar 12, 2013 at 6:23 PM, Logan McNaughton wrote:
>
>> For Quantum GRE tunneling, the network node and compute nodes need a NIC
>> on your data network. You assign each of those NIC's an IP (for instance,
>> 192.168.1.1-3). Then (assuming you are using openvswitch with GRE
>> tunneling) you set up your quantum configs. Look at the Quantum
>> administration guide for an example of GRE tunneling with openvswitch.
>>
>> After that you just let it work its magic. All VM traffic is encapsulated
>> inside GRE packets traveling between the nodes, it'll all look like packets
>> in that 192.168.1-3 network.
>>
>> Once the packet reaches its destination node, the GRE encapsulation is
>> removed and the VM packet is read.
>> On Mar 12, 2013 6:36 AM, "Aru s"  wrote:
>>
>>>  Hi,
>>>
>>> I am trying to configuring openstack with one controller and one network
>>> and two compute nodes.
>>> I am not able to understand how the communication of the VM's happens
>>> which are for the same tenant with same ip range but on the different
>>> compute hosts.
>>> Please help me to understand how GRE communication happens.
>>>
>>> Regards,
>>> Arumon
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] question on the GRE Communication

2013-03-14 Thread Aru s
Hi  Logan,

Thanks for the reply. I have one more question.
How we will check whether the tunneling is established or not?
I have gone through lot of documents of gre setup and all are says that the
"ovs-vsctl show" command will show the tunnel info.
Also is there a doc to understand how the magic happens for tunneling.

Regards,
Arumon


On Tue, Mar 12, 2013 at 6:23 PM, Logan McNaughton wrote:

> For Quantum GRE tunneling, the network node and compute nodes need a NIC
> on your data network. You assign each of those NIC's an IP (for instance,
> 192.168.1.1-3). Then (assuming you are using openvswitch with GRE
> tunneling) you set up your quantum configs. Look at the Quantum
> administration guide for an example of GRE tunneling with openvswitch.
>
> After that you just let it work its magic. All VM traffic is encapsulated
> inside GRE packets traveling between the nodes, it'll all look like packets
> in that 192.168.1-3 network.
>
> Once the packet reaches its destination node, the GRE encapsulation is
> removed and the VM packet is read.
> On Mar 12, 2013 6:36 AM, "Aru s"  wrote:
>
>>  Hi,
>>
>> I am trying to configuring openstack with one controller and one network
>> and two compute nodes.
>> I am not able to understand how the communication of the VM's happens
>> which are for the same tenant with same ip range but on the different
>> compute hosts.
>> Please help me to understand how GRE communication happens.
>>
>> Regards,
>> Arumon
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] question on the GRE Communication

2013-03-12 Thread Logan McNaughton
For Quantum GRE tunneling, the network node and compute nodes need a NIC on
your data network. You assign each of those NIC's an IP (for instance,
192.168.1.1-3). Then (assuming you are using openvswitch with GRE
tunneling) you set up your quantum configs. Look at the Quantum
administration guide for an example of GRE tunneling with openvswitch.

After that you just let it work its magic. All VM traffic is encapsulated
inside GRE packets traveling between the nodes, it'll all look like packets
in that 192.168.1-3 network.

Once the packet reaches its destination node, the GRE encapsulation is
removed and the VM packet is read.
On Mar 12, 2013 6:36 AM, "Aru s"  wrote:

> Hi,
>
> I am trying to configuring openstack with one controller and one network
> and two compute nodes.
> I am not able to understand how the communication of the VM's happens
> which are for the same tenant with same ip range but on the different
> compute hosts.
> Please help me to understand how GRE communication happens.
>
> Regards,
> Arumon
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] question on the GRE Communication

2013-03-12 Thread Aru s
Hi,

I am trying to configuring openstack with one controller and one network
and two compute nodes.
I am not able to understand how the communication of the VM's happens which
are for the same tenant with same ip range but on the different compute
hosts.
Please help me to understand how GRE communication happens.

Regards,
Arumon
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp