hello Ole,
yes, we have a control plane, and the protocols I mentioned below run in the
control plane.
when these protocols want to send packets, they organize their own protocol
data then call inet raw socket to set the IP header and link header. when
received a packet from the interface, first we will stripe the link header and
ip header then hand over to the corresponding modules through inet raw socket.
Now can you know what I want to do?
saint_sun
From: Ole Troan
Date: 2018-11-08 11:11
To: saint_sun
CC: vpp-dev
Subject: Re: [vpp-dev] inet raw socket
> Some protocols or functions need inet raw socket to transmit and receive
> packets such as ping/vrrp/pim, and I want to debug these functions.
You are still leaving me guessing at what you are trying to do.
You can implement these inside of VPP, where you obviously don’t need or use a
socket API.
Sounds like you are talking about having these protocols implemented on the
control plane side.
There are many ways of integrating a control plane with VPP.
With e.g. a port mirroring approach, you would use Linux applications
unchanged. That’s not necessarily where I would go. We have some ideas around
improvements for the CP/DP interface, and I’m happy to engage in a discussion
with that, but you would have to share what problem you are trying to solve in
more detail.
Best regards,
Ole
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11210): https://lists.fd.io/g/vpp-dev/message/11210
Mute This Topic: https://lists.fd.io/mt/27857220/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
