[prev in list] [next in list] [prev in thread] [next in thread] 

List:       juniper-nsp
Subject:    Re: [j-nsp] [c-nsp] LACP between router VMs
From:       James Bensley <jwbensley () gmail ! com>
Date:       2017-11-08 18:21:07
Message-ID: CAAWx_pVE_Ya4473u8=X0VLP_WfMRu_YWB1y-7uNSoesES3GJDw () mail ! gmail ! com
[Download RAW message or body]

On 8 November 2017 at 16:30, Jeff Meyers <Jeff.Meyers@gmx.net> wrote:
> Hi Adam,
>
> LACP packets (so called slow packets in the linux kernel) are never
> forwarded by the bridging code. If it didn't change in the last ~2 years,
> you will have to hack your kernel in order to let them pass. It's actually
> only a minor change in a couple of lines. The same applies btw to STP
> packets.
>
>
> Jeff
>
>
> Am 08.11.2017 um 17:09 schrieb adamv0025@netconsultings.com:
>>
>> Hi folks,
>>
>>
>> Slightly off topic but I'm gonna give it a shot anyways.
>>
>> Would anyone know how can I make linux bridges or better OVS to forward
>> LACP
>> PDUs instead of swallowing 'em?
>>
>> Basically "l2protocol forward lacp" equivalent.
>>
>> Couldn't find a single article on this and just can't believe I'm the
>> first
>> person that ever tried this.
>>
>> Aren't linux bridges or OVS MEF compliant :-) ?
>>
>>
>> Thanks
>>
>>
>> adam

If you have NIC(s) that support SR-IOV in your hypervisor boxes then
binding a virtual-function from the PF to your VMs should allow the
LACP frames to pass.

Cheers,
James,
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[prev in list] [next in list] [prev in thread] [next in thread]