[ovs-discuss] Fwd: GRE tunnel
sonia verma
soniaverma9727 at gmail.com
Thu Dec 12 09:54:34 UTC 2013
---------- Forwarded message ----------
From: sonia verma <soniaverma9727 at gmail.com>
Date: Thu, Dec 12, 2013 at 12:55 PM
Subject: Re: [ovs-discuss] GRE tunnel
To: kevin parker <kevin.parker092 at gmail.com>
Hi Kevin,
My set is as follows:
Hypervisor1
ovs-vsctl add-br br0
ovs-vsctl add-port br0 eth0
ovs-vsctl add-br br1
ovs-vsctl add-port br1 eth1
ifconfig br0 10.10.10.1 netmask 255.255.255.0 up
ifconfig br1 192.168.10.1 netmask 255.255.255.0 up
ovs-vsctl add-port br1 gre0 -- set interface gre0 type=gre
options:remote_ip=10.10.10.2
ip route add 192.168.20.0/24 via 10.10.10.2 dev br0
Hypervisor2
ovs-vsctl add-br br0
ovs-vsctl add-port br0 eth0
ovs-vsctl add-br br1
ovs-vsctl add-port br1 eth1
ifconfig br0 10.10.10.2 netmask 255.255.255.0 up
ifconfig br1 192.168.20.1 netmask 255.255.255.0 up
ovs-vsctl add-port br1 gre0 -- set interface gre0 type=gre
options:remote_ip=10.10.10.1
ip route add 192.168.10.0/24 via 10.10.10.1 dev br0
Both the hypervisors are connected to each other through their eth0
interfaces.
The host machines are connected to the respective hypervisors through eth1
interface.
The host machine connected to the hypervisor1 has 192.168.10.10 ip with
br1(192.168.10.1) as gateway.
Similary host 2 connected to hypervisor2 has 192.168.20.10 ip with
br1(192.168.20.1) as gateway.
The flow on all the bridges is normal.
Host1 is able to ping Host 2 via gre tunnel.But the wireshark capture on
br0 of hypervisor1 as well as hypervisor2 does not show any gre header.
Do I have to push rules on the ovs so as to enable gre header? If so how?
Wheather openvswitch support GRE in userspace or in kernelspace?
Thanks
On Thu, Dec 12, 2013 at 12:06 PM, kevin parker <kevin.parker092 at gmail.com>wrote:
> Can you post your setup details :
> also output of ovs-vsctl show from both hypervisors
> br0 ip on hypervisors
>
> If its all fine have you tried tcpdump
>
>
> On Wed, Dec 11, 2013 at 4:25 PM, sonia verma <soniaverma9727 at gmail.com>wrote:
>
>> Hi Kevin,
>>
>> I assigned Ip to bridge without using tep0 but still its not working .
>> Can you help regarding this?
>>
>>
>> On Wed, Dec 11, 2013 at 3:23 PM, kevin parker <kevin.parker092 at gmail.com>wrote:
>>
>>> Hi,
>>> I dont have any issue,i was trying to understand how it works.How
>>> broadcast traffic reaches from port gre0 to interface eth0.
>>>
>>> Also do you have ip assigned to br0 and tep0
>>> as i said i dont use tep0 instead i have assigned ip directly to br0,you
>>> only need tep0 if u dont have any ip assigned to bridge that connects
>>> physical interface.
>>>
>>>
>>>
>>> On Tue, Dec 10, 2013 at 3:52 PM, sonia verma <soniaverma9727 at gmail.com>wrote:
>>>
>>>> Hi Kevin
>>>>
>>>> I'm trying your setup in my lab.
>>>> I'm able to ping my my tunnel endpoint but not able to ping remote end
>>>> point.
>>>> Can you help regarding this?
>>>> Moreover what about your issue?Is it working fine.
>>>>
>>>> Also it will be helpful if you can forward any link regarding this so
>>>> that it may be easy for me to debug.
>>>>
>>>>
>>>> On Fri, Dec 6, 2013 at 4:51 PM, sonia verma <soniaverma9727 at gmail.com>wrote:
>>>>
>>>>
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: sonia verma <soniaverma9727 at gmail.com>
>>>>> Date: Fri, Dec 6, 2013 at 3:58 PM
>>>>> Subject: Re: [ovs-discuss] GRE tunnel
>>>>> To: kevin parker <kevin.parker092 at gmail.com>
>>>>>
>>>>>
>>>>> Hi Kevin
>>>>>
>>>>> Yes Kevin I assigned ip to tep0. I assigned the ip of hipervisor2 to
>>>>> tep0 of hypervisor1 and vice-versa.
>>>>>
>>>>> Thanks for the reply.I will let you know whether it configuration
>>>>> worked or not.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Sonia
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Dec 6, 2013 at 3:48 PM, kevin parker <
>>>>> kevin.parker092 at gmail.com> wrote:
>>>>>
>>>>>> Hi i dont use tep0,
>>>>>>
>>>>>> Dont know whether it can be useful to you:
>>>>>>
>>>>>> my setup is simple
>>>>>>
>>>>>> Hypervisor1: Hypervisor2:
>>>>>>
>>>>>> kvmbr0(public ip) xenbr0(public ip)
>>>>>> eth0 eth0
>>>>>>
>>>>>> isolated isolated
>>>>>> vif1.0 (private ip) vif1.0
>>>>>> (private ip)
>>>>>> gre0-->ip-hypervisor2
>>>>>> gre0-->hypervisor1
>>>>>>
>>>>>> Everything is working fine
>>>>>>
>>>>>> commands:
>>>>>> ovs-vsctl add-br isolated
>>>>>> ovs-vsctl add-port isolated gre0 -- set interface gre0 type=gre
>>>>>> options:remote_ip=ip of hypervisor
>>>>>>
>>>>>>
>>>>>> *Also did you assign any ip to tep0? *
>>>>>>
>>>>>> On Fri, Dec 6, 2013 at 3:35 PM, sonia verma <soniaverma9727 at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Kevin
>>>>>>>
>>>>>>> I'm trying the below link for the same functionality....
>>>>>>>
>>>>>>> http://linuxmantra.com/2013/08/gre-tunneling-with-open-vswitch.html
>>>>>>>
>>>>>>> I'm able to reach tep0 of Hypervisor1 from both the VMs but I wonder
>>>>>>> why I'm not able to reach tep0 of Hypervisor2 from VM1 and VM2.
>>>>>>>
>>>>>>> Could you help regarding this?
>>>>>>>
>>>>>>> It will be great if you share your set-up configuration with me so
>>>>>>> that We both may be able to look onto this.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks..
>>>>>>> Sonia...
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Dec 6, 2013 at 2:58 PM, kevin parker <
>>>>>>> kevin.parker092 at gmail.com> wrote:
>>>>>>>
>>>>>>>> Can any one please help me understand the invisible link that
>>>>>>>> carries traffic from gre0 through birdge with NIC attached.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Dec 5, 2013 at 10:10 PM, kevin parker <
>>>>>>>> kevin.parker092 at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>> I have a working GRE connected between one kvm host ovs
>>>>>>>>> 1.11 and xenserver ovs 1.4.6
>>>>>>>>>
>>>>>>>>> I have created an *isolated* bridge and connected virtual
>>>>>>>>> interface to isolated bridge with private ip ,and then added
>>>>>>>>> *gre0* port by mentioning remote public IP.
>>>>>>>>>
>>>>>>>>> Everything is fine, dont have any issues :)
>>>>>>>>>
>>>>>>>>> For understanding it better
>>>>>>>>>
>>>>>>>>> tried tcpdump on isolated bridge i am not able find anything other
>>>>>>>>> than ARP request
>>>>>>>>>
>>>>>>>>> *tcpdump -i isolated -n not port 22 -v*
>>>>>>>>>> tcpdump: listening on isolated, link-type EN10MB (Ethernet),
>>>>>>>>>> capture size 65535 bytes
>>>>>>>>>> 21:31:06.304223 ARP, Ethernet (len 6), IPv4 (len 4), Request
>>>>>>>>>> who-has 10.168.122.10 tell 10.168.122.200, length 28
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> so used dump-flows on ovs 1.4.6
>>>>>>>>> ovs-dpctl dump-flows isolated|grep -v 'src=22' |grep -v 'dst=22'
>>>>>>>>> in_port(3),eth(src=ae:0a:5e:8a:cc:2b,dst=52:54:00:bb:86:99),eth_type(0x0800),ipv4(src=10.168.122.200,dst=10.168.122.10,proto=1,tos=0,ttl=64,frag=no),icmp(type=8,code=0),
>>>>>>>>> packets:0, bytes:0, used:never, actions:*1*
>>>>>>>>>
>>>>>>>>> in_port(1),eth(src=52:54:00:bb:86:99,dst=ae:0a:5e:8a:cc:2b),eth_type(0x0800),ipv4(src=10.168.122.10,dst=10.168.122.200,proto=1,tos=0,ttl=64,frag=no),icmp(type=0,code=0),
>>>>>>>>> packets:0, bytes:0, used:never, actions:*3*
>>>>>>>>>
>>>>>>>>> From this if i understand correctly ovs is outputting to port 1
>>>>>>>>> which is *gre0* with remote ip .But i don't understand
>>>>>>>>> 1.how packets go from *gre0* through bridge *kvmbr0* in which NIC
>>>>>>>>> is bridged.
>>>>>>>>> and
>>>>>>>>> 2. tcpdump not showing any packets in isolated bridge.
>>>>>>>>>
>>>>>>>>> Can some one please help me understand this better or point to
>>>>>>>>> some documentation
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> kevin
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> discuss mailing list
>>>>>>>> discuss at openvswitch.org
>>>>>>>> http://openvswitch.org/mailman/listinfo/discuss
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20131212/63f344fc/attachment.html>
More information about the discuss
mailing list