On Thu, Oct 1, 2015 at 11:22 PM, Jiri Benc wrote:
> On Thu, 1 Oct 2015 22:19:10 -0700, Pravin Shelar wrote:
>> On Thu, Oct 1, 2015 at 9:08 AM, Jiri Benc wrote:
>> > This is for IPv4 only at this point. Only vxlan is recognized for now.
>> >
>> > The usage is as follows:
>> >
>> > ip l a type vxla
On Thu, 1 Oct 2015 22:19:10 -0700, Pravin Shelar wrote:
> On Thu, Oct 1, 2015 at 9:08 AM, Jiri Benc wrote:
> > This is for IPv4 only at this point. Only vxlan is recognized for now.
> >
> > The usage is as follows:
> >
> > ip l a type vxlan metadata dstport 4789
> > ovs-vsctl add-port ovsbridge vx
On Thu, Oct 1, 2015 at 9:08 AM, Jiri Benc wrote:
> This is for IPv4 only at this point. Only vxlan is recognized for now.
>
> The usage is as follows:
>
> ip l a type vxlan metadata dstport 4789
> ovs-vsctl add-port ovsbridge vxlan0
>
> Now, the encapsulation can be specified using ovs-ofctl, e.g.
On Thu, 1 Oct 2015 18:08:51 +0200, Jiri Benc wrote:
> This is for IPv4 only at this point. Only vxlan is recognized for now.
>
> The usage is as follows:
>
> ip l a type vxlan metadata dstport 4789
> ovs-vsctl add-port ovsbridge vxlan0
^ should be "ovs0"
> Now, the encapsul
This is for IPv4 only at this point. Only vxlan is recognized for now.
The usage is as follows:
ip l a type vxlan metadata dstport 4789
ovs-vsctl add-port ovsbridge vxlan0
Now, the encapsulation can be specified using ovs-ofctl, e.g.:
ovs-ofctl add-flow ovs0 'in_port=2
actions=set_field:2->tun
