[ovs-discuss] Issue when using local_ip with VXLAN tunnels in OVS

Gregory Rose gvrose8192 at gmail.com
Tue Nov 6 23:17:27 UTC 2018


On 11/6/2018 3:08 PM, Siva Teja ARETI wrote:
>
>
> On Tue, Nov 6, 2018 at 5:42 PM Gregory Rose <gvrose8192 at gmail.com 
> <mailto:gvrose8192 at gmail.com>> wrote:
>
>
>     On 11/6/2018 8:51 AM, Siva Teja ARETI wrote:
>>     Hi Greg,
>>
>>     Thanks for looking into this.
>>
>>     I have two VMs in my setup each with two interfaces. Trying to
>>     setup the VXLAN tunnels across these interfaces which are in
>>     different subnets. A docker container is attached to ovs bridge
>>     using ovs-docker utility on each VM and doing a ping from one
>>     container to another.
>
>     Hi Siva,
>
>     In reading through the documentation and looking at your
>     configuration I noticed that when using the
>     local_ip option the remote_ip is not set to flow. If the local_ip
>     option is specified then remote_ip must
>     equal flow.
>
>     From the documentation (man ovs-vswitchd.conf.db):
>
>            options : local_ip: optional string
>                   Optional.  The  tunnel destination IP that received
>     packets must
>                   match. Default is to match all addresses. If
>     specified,  may  be
>                   one of:
>
>                   ·      An IPv4/IPv6 address (not a DNS name), e.g.
>     192.168.12.3.
>
>                   ·      The  word flow. The tunnel accepts packets
>     sent to any of
>                          the local IP addresses of  the system 
>     running  OVS.  To
>                          process  only  packets sent to a specific IP
>     address, the
>                          flow entries may match on  the tun_dst  or 
>     tun_ipv6_dst
>                          field.  When  sending  packets to a
>     local_ip=flow tunnel,
>                          the flow  actions  may explicitly  set  the 
>     tun_src  or
>                          tun_ipv6_src field to the desired IP address,
>     e.g. with a
>                          set_field action. However, while  routing 
>     the  tunneled
>                          packet  out,  the local system may override
>     the specified
>                          address with the local IP address configured
>     for the out‐
>                          going system interface.
>
>                          This  option  is  valid  only for tunnels
>     also configured
>                          with the remote_ip=flow option.
>
>
> As I understand this documentation, option local_ip=flow can only be 
> specified when remote_ip=flow is also specified. Otherwise, ovs-vsctl 
> throws this error I guess?
>
> [root at vm1 ~]# ovs-vsctl add-port testbr0 vxlan1 -- set interface 
> vxlan1 type=vxlan options:local_ip=flow options:remote_ip=30.30.0.193 
> options:dst_port=4789
> ovs-vsctl: Error detected while setting up 'vxlan1': vxlan1: vxlan 
> type requires 'remote_ip=flow' with 'local_ip=flow'.  See ovs-vswitchd 
> log for details.
> ovs-vsctl: The default log directory is "/var/log/openvswitch".
>
>
>     Please try using the remote_ip=flow option and then configuring
>     the proper flow and action.
>
>
> Anyways, I also tried by specifying remote_ip=flow option when 
> creating the tunnel. But I still the same issue

I see.  It appears you are right and I misread the documentation. OK, 
l'll investigate further then.

- Greg


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20181106/a80fa256/attachment-0001.html>


More information about the discuss mailing list