> BTW: I've got things working now such that I can create VXLAN ports
> again. I just need to clean things up a bit and add add the code to handle
> tbl_backer management. With any luck I'll have some patches to send
> out today yet.
Awesome, sounds great.
Ethan
>
> Thanks,
> Kyle
>
>> Ethan
>>
On Feb 6, 2013, at 12:57 PM, Ethan Jackson
wrote:
>> I see an issue right now. It looks like netdev_vport_get_dpif_port()
>> currently just returns a const char * by returning a pointer to the dpif_port
>> pointer on vport_class. Modifying this behavior to return a dynamic
>> name here means we n
> I see an issue right now. It looks like netdev_vport_get_dpif_port()
> currently just returns a const char * by returning a pointer to the dpif_port
> pointer on vport_class. Modifying this behavior to return a dynamic
> name here means we need to allocate a char * pointer here and modify
> the c
On Feb 4, 2013, at 3:50 PM, Ethan Jackson wrote:
>> Yes, I'd like to help here. Can you shoot me any ideas you may have?
>> I've been looking at this in my free time today. Tomorrow I should be
>> able to dedicate most of the day to it.
>
> Ok sounds good. Thanks for taking this on.
>
Just ge
> Yes, I'd like to help here. Can you shoot me any ideas you may have?
> I've been looking at this in my free time today. Tomorrow I should be
> able to dedicate most of the day to it.
Ok sounds good. Thanks for taking this on.
So at a high level, conceptually what we need to do is fairly straig
On Feb 4, 2013, at 2:59 PM, Ethan Jackson wrote:
>> I figured this out. It looks like the flow based tunneling changes no longer
>> propagate the destination UDP port down to VXLAN, which requires it. Because
>> of this, the VXLAN vport code in the kernel is returning an error. I'll go
>> ahead
> I figured this out. It looks like the flow based tunneling changes no longer
> propagate the destination UDP port down to VXLAN, which requires it. Because
> of this, the VXLAN vport code in the kernel is returning an error. I'll go
> ahead and fix these up now.
Yep I noticed this last Friday
On Feb 3, 2013, at 8:56 PM, Kyle Mestery (kmestery) wrote:
> I'm running with the latest master, and I noticed I can no longer configure
> VXLAN ports. I'm tracking this down, but wanted to let folks on the list know
> as well.
>
> I am configure my VXLAN port like this:
>
>ovs-vsctl a
I'm running with the latest master, and I noticed I can no longer configure
VXLAN ports. I'm tracking this down, but wanted to let folks on the list know
as well.
I am configure my VXLAN port like this:
ovs-vsctl add-port br2 vxlan1 -- set interface vxlan1 \
type=vxlan o
