It shouldn't matter that you have two bridges, the only one that applies in
this case is br_vnet. I would use ovs-appctl dpif/dump-flows and
ofproto/trace to debug where your packets are currently going and then
write a flow to match using fields such as tun_id, tun_src, etc. similar to
what you are using on the transmit side.
On Wed, Sep 4, 2013 at 6:12 AM, Andrei Andone
<andrei.and...@softvision.ro>wrote:
> Hello Jesse,
>
> Sorry for the delay on my reply, I couldn't reply any sooner.
>
> To answer your question: No, I don't have a flow for receiving, because I
> couldn't really understand where I'm supposed to add the flow and how it
> should look like. I've seen examples with only one bridge but I'm using two
> bridges, as mentioned in the initial post and I could really use some
> hints/tips or anything to get this working.
>
> Thanks,
> Andrei
>
>
> On 08/30/2013 07:09 PM, Jesse Gross wrote:
>
> Do you have a corresponding flow to receive the VXLAN traffic? You only
> showed one for sending.
>
> As you mentioned before, you should be able to use ofproto/trace to see
> what OpenFlow rules are being hit.
>
>
> On Wed, Aug 28, 2013 at 4:48 AM, Andrei Andone <
> andrei.and...@softvision.ro> wrote:
>
>> Hello Jesse,
>>
>> Yes, on Wireshark listening to eth0, I see udp packets being sent and
>> received between the hosts (udp, destination port: 4789, which is vxlan
>> port). So the hosts are comunicating (the tunnel is) but I can't see any
>> reply on my br-vnet wireshark, or my VM receiving the answer that reached
>> the host.
>>
>> Thanks,
>> Andrei
>>
>>
>> On 08/28/2013 02:50 AM, Jesse Gross wrote:
>>
>> On Tue, Aug 27, 2013 at 5:51 AM, Andrei Andone <
>> andrei.and...@softvision.ro> wrote:
>>
>>> Hello guys,
>>>
>>> I have a question related to the "options:remote_ip=flow" feature.
>>>
>>> My config looks like this for one host:
>>>
>>> [root@localhost ~]# ovs-vsctl show
>>> e927ea5a-41d8-4bf5-9145-5be06e18bc9f
>>> Bridge "br-eth0"
>>> Port "br-eth0"
>>> Interface "br-eth0"
>>> type: internal
>>> Port "eth0"
>>> (external interface)
>>> Interface "eth0"
>>> Bridge br-vnet
>>> Port br-vnet
>>> Interface br-vnet
>>> type: internal
>>> Port "vxlan1"
>>> (tunnel I use)
>>> Interface "vxlan1"
>>> type: vxlan
>>> options: {key="10", remote_ip=flow}
>>> Port "vnet0"
>>> (port for the virtual machine)
>>> Interface "vnet0"
>>> ovs_version: "1.12.90"
>>> [root@localhost ~]#
>>>
>>> If I set the "options:remote_ip=A.A.A.1" (the IP for host 2) everything
>>> works just fine ARP requests from my VM, pings to the subnet, etc.
>>>
>>> If I leave it like this, it doesn't work.
>>>
>>> I followed some instructions that I could find by google-ing.
>>>
>>> I know I need to set up flows to transmit and to receive, but I'm not
>>> sure how.
>>> Until now, for transmitting I used:
>>>
>>> ovs-ofctl add-flow br-vnet
>>> "in_port=1,actions=set_field:A.A.A.1->tun_dst,output:2"
>>> (in_port = virtual network port, output = tunnel port)
>>>
>>
>> Do you actually see packets going out on the wire when they hit this
>> flow?
>>
>>
>> --
>> Andrei Andone
>>
>> SOFTVISION | 57 Republicii Street, 400489 Cluj-Napoca, Romania
>> Email: andrei.and...@softvision.ro | Web: www.softvision.ro
>>
>> The content of this communication is classified as SOFTVISION
>> Confidential and Proprietary Information.
>>
>
>
> --
> Andrei Andone
>
> SOFTVISION | 57 Republicii Street, 400489 Cluj-Napoca, Romania
> Email: andrei.and...@softvision.ro | Web: www.softvision.ro
>
> The content of this communication is classified as SOFTVISION Confidential
> and Proprietary Information.
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
