As stated by Dave, if you are doing L2 forwarding by putting the VM interfaces into a bridge domain, it will forward packets based on destination MAC address and would not be affected by ethertype nor L3/L4 headers. -John
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Dave Barach via Lists.Fd.Io Sent: Monday, March 18, 2019 7:25 AM To: Eyle Brinkhuis <eyle.brinkh...@surfnet.nl>; vpp-dev@lists.fd.io; John Lo (loj) <l...@cisco.com> Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Support for non TCP traffic If the idea is simply to flood and/or forward at L2 these ethertypes, there’s a decent chance you won’t have to do anything beyond bridge configuration. If you want to process them (e.g. in a plugin), a call to ethernet_register_input_type(...) will deliver the goods to your code. Copying John Lo, our L2 path expert... HTH... Dave From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> On Behalf Of Eyle Brinkhuis Sent: Monday, March 18, 2019 4:28 AM To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: [vpp-dev] Support for non TCP traffic Hi all, I couldn’t find an answer on the wiki for this case: We are looking into building a VM platform (on openstack) with vpp. For one of our use cases we’d need to provide interconnectivity between VM’s for a HA setup (in this case FortiGate VM’s for a HA firewallinsetup). These FWs make use of non-TCP packets with ethertype 0x8890, 0x8891 and 0x8993. Can VPP work with these? If not, what would be the solution here? Thanks, Regards, Eyle
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12577): https://lists.fd.io/g/vpp-dev/message/12577 Mute This Topic: https://lists.fd.io/mt/30471946/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
